UFPLA SAP (Change Document Structure; Generated by RSSCD000) Structure details
Dictionary Type: Structure
Description: Change Document Structure; Generated by RSSCD000
Description: Change Document Structure; Generated by RSSCD000
Structure field list including key, data, relationships and ABAP select examples
UFPLA is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Change Document Structure; Generated by RSSCD000" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_UFPLA TYPE UFPLA.
The UFPLA table consists of various fields, each holding specific information or linking keys about Change Document Structure; Generated by RSSCD000 data available in SAP. These include MANDT (Client), FPLNR (Billing plan number / invoicing plan number), FPTYP (Billing plan category), FPART (Billing/Invoicing Plan Type).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP UFPLA structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| FPLNR | Billing plan number / invoicing plan number | FPLNR | CHAR | 10 | Assigned to domain | FPLNR | |||
| FPTYP | Billing plan category | FPTYP_FP | CHAR | 1 | FPTYP | ||||
| FPART | Billing/Invoicing Plan Type | FPART | CHAR | 2 | TFPLA | FPART | |||
| SORTL | Sort field | SORTL | CHAR | 10 | CHAR10 | ||||
| BEDAT | Start date for billing plan/invoice plan | BEDAT_FP | DATS | 8 | DATUM | ||||
| ENDAT | End date billing plan/invoice plan | ENDAT_FP | DATS | 8 | DATUM | ||||
| HORIZ | Rule for Determining Horizon in Billing/Invoicing Plan | HORIZ_FP | CHAR | 2 | TVRG | VDREG_VEDA | |||
| VBELN | Sales and Distribution Document Number | VBELN | CHAR | 10 | VBUK | ALPHA | VBELN | AUN | |
| BEDAR | Rule for Origin of Start Date of Billing/Invoicing Plan | BEDAT_FPK | CHAR | 2 | TVRG | VDREG_VEDA | |||
| ENDAR | Rule for Origin of End Date for Billing/Invoicing Plan | ENDAT_FPK | CHAR | 2 | TVRG | VDREG_VEDA | |||
| PERIO | Rule for Origin of Next Billing/Invoice Date | PERIO_FP | CHAR | 2 | TVRG | VDREG_VEDA | |||
| FPLAE | Length of a standard period in the billing plan | FPLAE | NUMC | 3 | NUM3 | ||||
| RFPLN | Standard Billing/Invoicing Plan Number | RFPLN_D | CHAR | 10 | FPLA | FPLNR | |||
| LODAT | Dates from | TADAT | DATS | 8 | DATUM | ||||
| AUTTE | Billing/Invoice Creation in Advance | AUTTE | CHAR | 1 | XFELD | ||||
| LODAR | Rule for Origin of Start Dates | LODAR | CHAR | 2 | TVRG | VDREG_VEDA | |||
| PERAF | Rule for Determination of a Deviating Billing/Invoice Date | PERAF_FP | CHAR | 2 | TVRG | VDREG_VEDA | |||
| FAKCA | Calendar for Defining Days Relevant to Billing/Invoicing | FAKCA | CHAR | 2 | TFACD | WFCID | |||
| TNDAT | Dates to | TBDAT | DATS | 8 | DATUM | ||||
| TNDAR | Rule for Origin of End Dates | TBDAR | CHAR | 2 | TVRG | VDREG_VEDA | |||
| AUFPL | Routing number of operations in the order | CO_AUFPL | NUMC | 10 | AUFPL | ||||
| APLZL | General counter for order | CO_APLZL | NUMC | 8 | Assigned to domain | CO_APLZL | |||
| RSNUM | Number of Reservation/Dependent Requirement | RSNUM | NUMC | 10 | Assigned to domain | RSNUM | RES | ||
| RSPOS | Item Number of Reservation/Dependent Requirement | RSPOS | NUMC | 4 | RSPOS | RPO | |||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | EKKO | ALPHA | EBELN | BES | MEKK_C |
| FPLTU | Item unlimited in value | FPLTU | NUMC | 6 | Assigned to domain | FPLTR | |||
| AUST1 | Payment cards: Status regarding requirements | AUST1_CC | CHAR | 1 | AUST1_CC | ||||
| AUST2 | Payment cards: Totals status - Call external system | AUST2_CC | CHAR | 1 | CCALL | ||||
| AUST3 | Payment cards: Overall status - Responses from ext. system | AUST3_CC | CHAR | 1 | REACT_SD | ||||
| AUST4 | Payment cards: Reserve | AUST4_CC | CHAR | 1 | CHAR1 | ||||
| AUST5 | Payment cards: Authorization block | AUST5_CC | CHAR | 1 | XFELD | ||||
| BASISWRT | Target value | BASISWRT | CURR | 15(2) | WERTV8 | ||||
| PSPNR | WBS Element | PS_POSNR | NUMC | 8 | Assigned to domain | ABPSP | PS_POSNR | ||
| AUTKOR | Automatic creation of correction dates in billing plan | AUTKOR | CHAR | 1 | XFELD | ||||
| .INCLU--AP | 0 | ||||||||
| SUPLN | Subsequent billing plan number | /SAPHT/SW_SUPLN | CHAR | 10 | Assigned to domain | FPLNR | |||
| SYNCH | Billing plan automatic synchronization indicator | /SAPHT/SW_SYNCH | CHAR | 1 | /SAPHT/SW_SYNCH | ||||
| KUDAT | Cancellation date billing plan | /SAPHT/SW_KUDAT_FP | DATS | 8 | DATUM | ||||
| KUDAR | Rule for origin of billing plan cancellation date | /SAPHT/SW_KUDAT_FPK | CHAR | 2 | TVRG | VDREG_VEDA | |||
| KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
| Key field | Non-key field |
How do I retrieve data from SAP structure UFPLA using ABAP code?
As UFPLA is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on UFPLA as there is no data to select.How to access SAP table UFPLA
Within an ECC or HANA version of SAP you can also view further information about UFPLA and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects