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_SDSOURCEIDOC | Check Location of Data in IDoc Segments |
| Transaction Code | S_P7D_67000234 | (empty) |
| Created on | 20090304 | |
| Customizing Attributes | IDMX_DI_SDSOURCEIDOC | Check Location of Data in IDoc Segments |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | IDMX_DI_SDSOURCEIDOC |
Use
In this Customizing activity, you find the fields in the intermediate documents (IDocs) that contain the data you require to generate an XML file.
To enable the system to send the required data to an external system that generates an XML file of the digitally signed invoice, during the digital signature process, the system saves the required data in specific IDoc segments. There are two kinds of segments, qualified and non-qualified.
Non-qualified segments can be used only a single time within an IDoc, whereas qualified segments can be used more than once. There are two ways in which the system stores data, either directly within the segment or indirectly within a related child segment. The system accesses the data by means of qualifier values, which are fixed values of a domain.
Since there is not a one-to-one relationship between all the data in the original input message and particular fields in IDoc segments, we recommend that you derive the required data, for example, a location's reference or the second district, in the sender system before you send the IDoc to the target system that generates the XML file. You derive the required data and store them in enhanced segments of an IDoc of basic type INVOIC02.
Requirements
You have performed all other Customizing activities under Digital Signature Settings in this section.
You have set up your system to be able to send IDocs to external systems in Customizing for SAP NetWeaver under Application Server -> IDoc Interface / Application Link Enabling (ALE).
For more information, see SAP Library for SAP NetWeaver in SAP Help Portal at http://help.sap.com under SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> Platform-Wide Services -> Connectivity -> Components of SAP Communication Technology -> Classical SAP Technologies (ABAP) -> IDoc Interface/ALE.
Standard settings
Activities
- Create an IDoc of basic type INVOIC02.
- Send the IDoc to the required target system.
- When the system that you are going to use to generate the XML file has received the IDoc, to generate the XML file, map the target fields in the XML file with the corresponding fields in the IDoc.
For details about the fields in IDoc segments in which the system stores the data that you use to generate the XML file, see the Mapping_OIM_Blocks_to_IDoc_SD document attached to SAP Note 1303712.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| IDMX_DI_SDSOURCEIDOC | MX | Mexico |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | IDMX_DI_SDSOURCEIDOC | 0 | HLA0009603 | Billing |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20090304 |
| SAP Release Created in | 600 |
