Hierarchy
⤷ CA (Application Component) Cross-Application Components
⤷ WPOS_IDOC_ABA (Package) POS IDocs R/3 Inbound and POSDW
Basic Data
Data Element | POSCARDGUID |
Short Description | GUID of a Payment Card |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SYSUUID | |
Data Type | RAW | Uninterpreted sequence of bytes |
Length | 16 | |
Decimal Places | 0 | |
Output Length | 32 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 4 | GUID |
Medium | 4 | GUID |
Long | 18 | GUID Payment Card |
Heading | 18 | GUID Payment Card |
Documentation
Definition
GUID that identifies the payment card number when payment card encryption is activated. This ID can be either unique or non-unique.
Use
The GUID is used to identify the payment card number when processing payment card information sent from the POS system to the SAP system, after being encrypted in accordance with the PCI (Payment Card Industry) rules. The GUID is specified internally by the SAP system, and does not need to be defined by the sending application (POS, POS converter, EDI subsystem or the POS interface). When sending credit card details to an SAP system through the POS IDoc interface, we recommend that you use additional security mechanisms (such as secure protocols); IDocs are not currently suitable for recording encrypted payment card numbers.
Dependencies
If the field is filled, it contains a masked value for the payment card number in the credit card segment of the IDoc (in accordance with the SAP system settings for payment card security), so making the original card number invisible.
Example
History
Last changed by/on | SAP | 20080418 |
SAP Release Created in |