Table
|
Name
|
Remarks
|
TFKKBRFAPPLCLASS
|
Application Class: Additional Settings
|
|
TFKKBRFBUFFER
|
Reserved Buffer Elements
|
|
Showing posts with label Transparent Table. Show all posts
Showing posts with label Transparent Table. Show all posts
Friday, December 28, 2018
Collection Strategy: BRF: Tips 11: Config Tables
Friday, March 16, 2012
Loans (Part 3)
Define Loan Categories
This IMG activity allows creation of default values for a loan category. These default values are proposed when a corresponding loan is created.
Initial Screen:
Table: TEK060T - Installment Plan and Loan Categories
Second Screen:
Table: TEK060A - Loan Categories
Installment Interval: the length of the intervals between the installments. The system determines the due dates of the installments using the start date, the installment interval, and the interval category.
Interval Type: the interval between installments. The system determines the due date for installments from the start date, the installment inervals, and the interval type. Standard Values:
1 = Days
2 = Weeks
3 = Months
4 = Every 2 Weeks
Sub-transaction for items due in return payment plan: In some application areas, this indicator determines parameters such as the interest key as well as the due dates. You cannot change the main transaction - it is determined via the internal main transaction 0085. In contrast to the installment plan where you cannot change the sub-transaction for the installments, here you can use a separate sub-transaction.
Sub-transaction for credit posting from loans: When you enter a loan repayment plan, the system automatically triggers the posting of the available credit. The sub-transaction to be used can be defaulted here.
Sub-transaction for posting receivables from loans: Once a loan repayment plan has been entered, this automatically triggers the posting of the receivable to the amount of the available credit. This receivables posting forms the basis of the loan repayment plan. The sub-transaction to be used can be defaulted here.
This IMG activity allows creation of default values for a loan category. These default values are proposed when a corresponding loan is created.
Initial Screen:
Table: TEK060T - Installment Plan and Loan Categories
Second Screen:
Table: TEK060A - Loan Categories
Installment Interval: the length of the intervals between the installments. The system determines the due dates of the installments using the start date, the installment interval, and the interval category.
Interval Type: the interval between installments. The system determines the due date for installments from the start date, the installment inervals, and the interval type. Standard Values:
1 = Days
2 = Weeks
3 = Months
4 = Every 2 Weeks
Sub-transaction for items due in return payment plan: In some application areas, this indicator determines parameters such as the interest key as well as the due dates. You cannot change the main transaction - it is determined via the internal main transaction 0085. In contrast to the installment plan where you cannot change the sub-transaction for the installments, here you can use a separate sub-transaction.
Sub-transaction for credit posting from loans: When you enter a loan repayment plan, the system automatically triggers the posting of the available credit. The sub-transaction to be used can be defaulted here.
Sub-transaction for posting receivables from loans: Once a loan repayment plan has been entered, this automatically triggers the posting of the receivable to the amount of the available credit. This receivables posting forms the basis of the loan repayment plan. The sub-transaction to be used can be defaulted here.
Wednesday, January 13, 2010
EVER
Extraction from SAP System
NOTE* : common used fields are highlighted in yellow.
| No. | Field | Description |
| 1 | MANDT | Client |
| 2 | VERTRAG | Contract |
| 3 | BUKRS | Company Code |
| 4 | SPARTE | Division |
| 5 | EIGENVERBR | Plant or company consumption |
| 6 | KOFIZ | Account determination ID for IS-U contra |
| 7 | PORTION | Alternative portion |
| 8 | ABSLANFO | Budget billing request for debtor |
| 9 | ABSZYK | Overrriding BB cycle on contract level |
| 10 | ABSMNANP | Do not adjust budget billing amount auto |
| 11 | GEMFAKT | Invoice Contracts Jointly (Mandatory Con |
| 12 | MANABR | Bill contract manually |
| 13 | ABRSPERR | Reason for blocking billing |
| 14 | ABRFREIG | Reason for releasing billing |
| 15 | BSTATUS | Processing status |
| 16 | KOSTL | Cost Center |
| 17 | VBEZ | Text for contract |
| 18 | VBEGINN | Start of contract |
| 19 | EINZDAT_ALT | Move-in date from legacy system |
| 20 | VENDE | End of contract |
| 21 | KUENDDAT | Cancellation date of contract |
| 22 | KFRIST | Number of time units for cancellation |
| 23 | KUENPER | Time unit for cancellation |
| 24 | VBISDAT | Renewal date of contract |
| 25 | VERLAENG | Number of time units for renewal |
| 26 | VERPER | Time unit for renewal |
| 27 | VABSCHLEVU | Date on which utility concluded the cont |
| 28 | VABSCHLKND | Date on which customer concluded the con |
| 29 | VABSCHLKNDTI | Time at which customer signed contract |
| 30 | PERSNR | Personnel Number |
| 31 | VREFER | Contract number from legacy system |
| 32 | ERDAT | Date on Which Record Was Created |
| 33 | ERNAM | Name of Person who Created the Object |
| 34 | AEDAT | Changed On |
| 35 | AENAM | Name of Person Who Changed Object |
| 36 | BEGRU | Authorization Group |
| 37 | LOEVM | Deletion Indicator |
| 38 | TXJCD | Tax Jurisdiction |
| 39 | MANOUTSORT | Reason for manual outsorting in billing |
| 40 | FAKTURIERT | Contract has already been invoiced |
| 41 | AUFNR | Order Number |
| 42 | PS_PSP_PNR | Work Breakdown Structure Element (WBS El |
| 43 | PRCTR | Profit Center |
| 44 | COPAKONT | Indicator: Profitability segment assigne |
| 45 | AUSGRUP | Outsorting check group for billing |
| 46 | OUTCOUNT | Number of manual outsortings to be carri |
| 47 | PYPLT | Payment plan type |
| 48 | PYPLS | Starting month of payment plan |
| 49 | GSBER | Business Area |
| 50 | SEGMENT | Segment for Segmental Reporting |
| 51 | SERVICEID | Service Provider |
| 52 | SRVPRVREF | Reference number of service provider |
| 53 | BILLMETHOD | Billing method |
| 54 | STAGRUVER | Statistics group for contract |
| 55 | PYPLA | Alternative start month of payment plan |
| 56 | BILLFINIT | Contract terminated for billing reasons |
| 57 | BFA_DEB_STAT | Payment plan - BF amount not released fo |
| 58 | BFA_CRED_STAT | Payment plan - BF amount not released fo |
| 59 | SALESEMPLOYEE | Sales employee |
| 60 | SALESPARTNER | Sales partners |
| 61 | SALESDOCUMENT | Sales and Distribution Document Number |
| 62 | PS_STARTDAT | Start Date of Payment Scheme (PS) |
| 63 | SERVPROV_PAY | Payment Class |
| 64 | INVOICING_PARTY | Service Provider That Invoices the Contr |
| 65 | COKEY | CO account assignment key, IS-U contract |
| 66 | BUPLA | Business Place |
| 67 | CONTRACTCLASS | Contract Class |
| 68 | CANCREASON | Reason for Cancellation of Contract |
| 69 | CANCREASON_NEW | Cancellation Reason (CRM) |
| 70 | EXTRAPOLWASTE | Category of Waste Disposal Budget Billin |
| 71 | PPM_CONTRACT | Identifies Contract as Prepayment Meter |
| 72 | OSB_GROUP | On-Site Billing Group |
| 73 | OUCONT | Outline Contract |
| 74 | RULEGR | Rule Group for Outline Agreements |
| 75 | REGIOGROUP | Regional structure grouping |
| 76 | CMGRP | Collection Management: Master Data Group |
| 77 | STRAT | Collection Strategy |
| 78 | CPERS | Collections Contact Person |
| 79 | ANLAGE | Installation |
| 80 | VKONTO | Contract Account Number |
| 81 | KZSONDEINZ | Move-In Processing (Special Case) |
| 82 | KZSONDAUSZ | Special move-out processing case exists |
| 83 | AUTEIGEINZ | Automatic Owner Move-In |
| 84 | EINZDAT | Move-In Date |
| 85 | AUSZDAT | Move-Out Date |
| 86 | ABSSTOPDAT | Stop date for budget bill. requests in t |
| 87 | SCHLFAKT | Joint final billing for move-in/out |
| 88 | MAHNV | Dunning Procedure |
| 89 | MAHNVUMZ | Move-in/out dunning procedure |
| 90 | MANSP | Dunning Lock Reason |
| 91 | BEZUG | Reference |
| 92 | TRANSVER | Transfer contract |
| 93 | SSWTCREASON | Reasons for contract change |
| 94 | XVERA | Contract created due to data transfer |
Subscribe to:
Posts (Atom)