UFPLTC SAP (Change Document Structure; Generated by RSSCD000) Structure details
Description: Change Document Structure; Generated by RSSCD000
Structure field list including key, data, relationships and ABAP select examples
UFPLTC 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_UFPLTC TYPE UFPLTC.
The UFPLTC 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), FPLTR (Item for billing plan/invoice plan/payment cards), CCINS (Payment cards: Card 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 UFPLTC 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 | FPLA | FPLNR | |||
FPLTR | Item for billing plan/invoice plan/payment cards | FPLTR | NUMC | 6 | FPLT | FPLTR | |||
CCINS | Payment cards: Card type | CCINS | CHAR | 4 | TVCIN | CCINS | |||
CCNUM | Payment cards: Card number | CCNUM | CHAR | 25 | Assigned to domain | CCNUM | |||
CCFOL | Payment cards: Payment card suffix | CCFOL | CHAR | 10 | CHAR10 | ||||
DATAB | Payment cards: Valid from | DATAB_CC | DATS | 8 | DATUM | ||||
DATBI | Payment Cards: Valid To | DATBI_CC | DATS | 8 | DATUM | ||||
CCNAME | Payment cards: Name of cardholder | CCNAME | CHAR | 40 | TEXT40 | ||||
CSOUR | Payment cards: Entry mode | CSOUR | CHAR | 1 | CSOUR | ||||
AUTWR | Payment cards: Authorized amount | AUTWR | CURR | 15(2) | WERTV8 | ||||
CCWAE | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
SETTL | Payment cards: Settlement carried out | SETTL | CHAR | 1 | XFELD | ||||
AUNUM | Payment cards: Authorization number | AUNUM | CHAR | 10 | CHAR10 | ||||
AUTRA | Payment cards: Authoriz. reference code of clearing house | AUTRA | CHAR | 15 | CHAR15 | ||||
AUDAT | Payment cards: Authorization date | AUDAT_CC | DATS | 8 | DATUM | ||||
AUTIM | Payment cards: Authorization time | AUTIM | TIMS | 6 | UZEIT | ||||
MERCH | Payment cards: Merchant ID at the clearing house | MERCH | CHAR | 15 | TCCM | MERCH | |||
LOCID | Payment cards: Point of receipt for the transaction | LOCID_CC | CHAR | 10 | TCCL | LOCID_CC | |||
TRMID | Payment cards: Terminal | TRMID | CHAR | 10 | CHAR10 | ||||
CCBTC | Payment cards: Settlement run | CCBTC | CHAR | 10 | ALPHA | CCBTC | |||
CCTYP | Payment cards: Card category | CCTYP | CHAR | 2 | TVCTY | CCTYP | |||
CCARD_GUID | Reference to Encrypted Payment Card Data | CCARDEC_GUID | CHAR | 32 | SYSUUID_C | ||||
CCAUA | Payment cards: Authorization type | CCAUA | CHAR | 1 | CCAUA | ||||
CCALL | Payment cards: Status when external system is called? | CCALL | CHAR | 1 | CCALL | ||||
REACT | Payment cards: Response to authorization checks | REACT_SD | CHAR | 1 | REACT_SD | ||||
AUTWV | Payment cards: Amount to be authorized | AUTWV | CURR | 15(2) | WERTV8 | ||||
CCOLD | Payment cards: Authorization has expired | CCOLD | CHAR | 1 | XFELD | ||||
CCVAL | Payment cards: Amount changed | CCVAL | CHAR | 1 | XFELD | ||||
CCPRE | Payment cards: Preauthorization | CCPRE | CHAR | 1 | XFELD | ||||
UELTR_A | Higher-level authorization for billing plan | UELTR_A | NUMC | 6 | FPLT | FPLTR | |||
RCAVR | Payment Cards: Result of Address Check (Address Result) | RCAVR_CC | CHAR | 4 | TCCRC | CHAR4 | |||
RCAVA | Payment Cards: Result of Address Check (Address Approval) | RCAVA_CC | CHAR | 4 | TCCRC | CHAR4 | |||
RCAVZ | Payment Cards: Result of Address Check (ZIP Code Result) | RCAVZ_CC | CHAR | 4 | TCCRC | CHAR4 | |||
RCRSP | Payment cards: Result of card check (response code) | RCRSP_CC | CHAR | 4 | TCCRC | CHAR4 | |||
RTEXT | Payment cards: Result text | RTEXT_CC | CHAR | 40 | TXT40 | ||||
KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
Key field | Non-key field |
How do I retrieve data from SAP structure UFPLTC using ABAP code?
As UFPLTC 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 UFPLTC as there is no data to select.How to access SAP table UFPLTC
Within an ECC or HANA version of SAP you can also view further information about UFPLTC 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