SAP ABAP Data Element IDMX_DI_PROFILE (Profile ID)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ FI-LOC (Application Component) Localization
⤷ ID-MX-DI (Package) Localization Mexico - Digital Invoice
⤷ FI-LOC (Application Component) Localization
⤷ ID-MX-DI (Package) Localization Mexico - Digital Invoice
Basic Data
Data Element | IDMX_DI_PROFILE |
Short Description | Profile ID |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | IDMX_DI_PROFILES | |
Data Type | CHAR | Character String |
Length | 15 | |
Decimal Places | 0 | |
Output Length | 15 | |
Value Table | IDMX_DI_PSEPROF |
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 | 10 | Prof. ID |
Medium | 15 | Profile ID |
Long | 20 | Profile ID |
Heading | 10 | Prof. ID |
Documentation
Definition
Shows the name of a specific set of SSF attributes that the system uses to process PSE files during the digital signature process.
Procedure
You use the SSF parameter to distinguish between different PSE files, or different attributes for PSE files. If required, you can, for example, use different PSE files for different organizational units in a given company code. You use the profile ID to control the following set of attributes:
- Code page
You specify the code page that the issuer and receiver of the digital invoice use, in line with current legal regulations. The system requires the code page for the character string when it determines the hash value, which is the basis for creating digital signatures. For example, code page UTF-8. - SSF hash algorithm
You specify the hash algorithm, for example, MD5, that complies with current legal regulations. The system uses the hash algorithm to generate the message digest in the format and length required by the authorities in Mexico. The system applies the sender's private key to the message digest (see SSF profile below). - Format of digital signature
You specify the version of the Public Key Cryptography Standards (PCKS) format, for example, PCKS#1 Padding Algorithm V1.5, that complies with current legal regulations. In addition to the hash algorithm, the system also requires the format of the digital signature that you must use with a particular PSE file. - SSF profile
You enter the name of the PSE file that contains the public key certificate and private key that the system uses to encrypt the message digest. For example, SAPMXDI_Filenameoffice1_100.pse.
Examples
Dependencies
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 600 |