Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
FI-LOC (Application Component) Localization⤷
ID-MX-DI (Package) Localization Mexico - Digital Invoice
IMG Activity
| ID | IDMX_DI_VPSEPROF | Enter SSF Profile Parameters |
| Transaction Code | S_P7D_67000207 | (empty) |
| Created on | 20090107 | |
| Customizing Attributes | IDMX_DI_VPSEPROF | Enter SSF Profile Parameters |
| Customizing Activity | IDMX_DI_VPSEPROF | Enter SSF Profile Parameters |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | IDMX_DI_VPSEPROF |
Use
In this Customizing activity, you create the SSF profiles that the system needs to process PSE files as part of the process of digitally signing electronic invoices in your company.
After the system generates the character string for a digital signature, the system uses the SSF profiles in this Customizing activity to determine the attributes that it must use to digitally sign electronic invoices for a given organizational unit.
In addition to the organizational validity, the SSF profile, and therefore the PSE file, is also valid for a specific period of time, for example, 2 years. However, you must specify the time frame in which you can use the PSE file, that is, the usage period for the PSE file. You specify the validity period of PSE files in the Customizing activity Specify Validity of SSF Profiles.
The system requires the following attributes for each SSF profile:
- 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.
If required, you can differentiate between different parts of your organization by creating multiple sets of attributes for a PSE file. For example, you can use a PSE file for certain sales offices or other organizational units, or for your whole organization.
Requirements
You have imported and saved the PSE file as described in the Customizing activity Save PSE File.
Standard settings
Activities
- Decide at which level in your organization you require a security profile, for example, at company code or sales office level.
By default, the system uses the same PSE file and attributes for your whole company code. - For each sales office, for example, create a unique profile ID for the SSF profile and enter the required data about the code page, hash algorithm, PSE file format, and the name of the PSE file.
Note: As soon as a PSE file expires, remove it from your system, because once a file expires, the SAP Cryptographic Library prevents the system from using that file.
Example
In your organization, you have two sales offices for Mexico City.
To increase the level of security that a digital invoice provides, you want to use a different PSE file for each sales office. In this Customizing activity, you create SSF profiles as follows:
ID for SSF Profile SSF Profile Name
MXOFF1 SAPMXDI_Filenameoffice1_100.pse
MXOFF2 SAPMXDI_Filenameoffice2_100.pse
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| IDMX_DI_VPSEPROF | MX | Mexico |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | IDMX_DI_VPSEPROF | 0 | HLA0009603 O HLA0009203 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IDMX_DI_VPSEPROF | V - View | SM30 |
History
| Last changed by/on | SAP | 20090320 |
| SAP Release Created in | 605 |
