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_SOURCE_OIMFI | Check Data Sources Required to Form Original Input Message |
| Transaction Code | S_P7D_67000241 | (empty) |
| Created on | 20090325 | |
| Customizing Attributes | IDMX_DI_SOURCE_OIMFI | Check Data Sources Required to Form Original Input Message |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | IDMX_DI_SOURCE_OIMFI |
Use
In this Customizing activity, you check the sources of the data that the system uses to compile the original input message (OIM).
You use the data listed in the Source of Data in Original Input Message table to check that the data the system requires for the OIM is stored in the correct place in your system, and where required, that you have used a Business Add-In (BAdI) implementation to incorporate the required data in the OIM.
The table below shows the combination of a group and field in the OIM, as defined by the Mexican authorities. To enable the system to form the OIM in the required order, the system must concatenate data for the individual fields in each group in a specific order. This means that there is not a one-to-one relationship between the groups defined by law and the groups that the system uses to form the OIM.
Since the system works with numbers and the legal definition works with letters for the fields within a group, you must use the latest legal definition of the OIM to find the internal number that the system uses for that field in the legal definition of the OIM. For example, field a in the group for document data corresponds to field 1 in the system, field b corresponds to field 2, and so on. The system numbers the fields in each group in consecutive, ascending numerical order. If the government introduces an additional field between a and b (a1, aa, or ab, for example) the internal number that the system assigns to that field will be 2, because it is the second field in that particular group. That therefore affects all subsequent numbers in that group.
For example, assume there is a problem with the contents of the data in one of the fields. The system outputs an error message that refers to group 1, field 3. Based on the contents in the table below, this combination corresponds to the following data in the legal definition of the OIM: field c (official document number) in the Document Data group.
Requirements
Standard settings
Activities
Check the sources of data for each part of the original input message. For example, if your master data or Customizing settings are incomplete or incorrect, you can use the table below to identify fields or settings that you need to change.
Group in Legal Definition of OIM Field in Legal Definition of OIM Group in System to Form OIM Index of Field in System Data Source in System
Document data a. Version Group 1 Index 1 The XML Version field in the Customizing activity Specify XML Version for Digital Invoice.
Document data b. Official document prefix Group 1 Index 2 The Reference Document Number (XBLNR) field in the Billing Document: Header (VBRK) table.
Document data c. Official document number Group 1 Index 3 The Reference Document Number (XBLNR) field in the Billing Document: Header (VBRK) table.
Document data d. Date and time Group 1 Index 4 The Date on Which Record Was Created (ERDAT) and Entry Time (ERZET) fields in the Billing Document: Header (VBRK) table.
Document data e. Approval number Group 1 Index 5 The Approval Number field in the Customizing activity Assign Number Range for a combination of company code, document class, and approval year.
Document data f. Approval year Group 1 Index 6 The Approval Year field in the Customizing activity Assign Number Range for a combination of company code, document class, and approval number.
Document data g. Document type Group 1 Index 7 Derived based on the document type that you define in the Customizing activity Define Billing Types. Based on the billing type, the system inserts the corresponding text in line with Mexican law: ingreso (income), egreso (expense), or traslado (transfer).
Document data h. Payment method Group 1 Index 8 Based on the setting of the Installment Payment checkbox in the Customizing activity Define Terms of Payment. If you do not select the checkbox, or select the checkbox and enter only one installment, the system inserts the Spanish text Pago en una sola exhibición (only one payment). If there is more than one installment, the system enters the Spanish text Pago en <(número de pagos parciales)> parcialidades (payment made in <(number of partial payments)> partial payments).
Document data i. Payment terms Group 1 Index 9 For a combination of the language in the billing document and the ID of the Terms of Payment (ZTERM) field, the system reads the payments terms from the Customers: Terms of Payment Texts table in the language of the billing document.
Document data j. Subtotal Group 1 Index 10 The sum of each item multiplied by the unit price; without any surcharges, discounts, or taxes. The system reads the subtotal from the Subtotal 1 from pricing (KZWI1) field in the Billing Document: Item Data (VBRP) table.
Document data k. Discount Group 1 Index 11 The system calculates the total discounts by subtracting the subtotal (Subtotal 1 from pricing procedure for condition (KZWI1) field in the Billing Document: Item Data (VBRP) table from the net total (the Net value of the billing item in document currency (NETWR) field in the Billing Document: Item Data (VBRP) table).
Document data l. Total Group 1 Index 12 The system adds the subtotal less any discounts (see above) to the taxes stored in the Tax amount in document currency (MWSBK) field in the Billing Document: Header Data (VBRK) table.
Document data m. Means of Payment Group 1 Index 13 The way that the payment has been done, such as by bank transfer, cash or credit card. The system populates this field by taking the value in Spanish assigned to the field TEXT1 of the table T042Z
Document data n. Issuing Place Group 1 Index 14 The place where the invoice has been issued. The system reads from the company code the fields CITY and STATE and displays them separated by a space.
Document Data o. Account Number Group 1 Index 15 The account number assigned to the means of payment. The system reads the Bank Key from (BANKL) from Customer Master (Bank Details) table (KNBK).
Document Data p. Exchange Rate Group1 Index 16 The exchange rate of the document. The system reads the Exchange rate (KURSF) field from the Accounting Document Header table (BKPF)
Document Data q. Document Currency Group 1 Index 17 The currency of the document. The system reads the Currency Key (WAERS) field from the Accounting Document Header table (BKPF)
Document Data r. Original Folio Group 1 Index 18 The number of the original document which payment is split into installments. Field is populated if Get Installment Data of Original Document BAdI method is implemented.
Document Data s. Original Prefix Group 1 Index 19 The series of the original document which payment is split into installments. Field is populated if Get Installment Data of Original Document BAdI method is implemented.
Document Data t. Original Date Group 1 Index 20 The creation date ofthe original document which payment has been split into installments. Field is populated if Get Installment Data of Original Document BAdI method is implemented.
Document Data u. Original Amount Group 1 Index 21 The total amount of the original document which payment has been split into installments. Field is populated if Get Installment Data of Original Document BAdI method is implemented.
Company code global data a. Company's tax number Group 2 Index 1 The tax number stored in the Parameter Value (PAVAL) field in the Additional Specifications for Company Code (T001Z) table for the respective company code with the
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| IDMX_DI_SOURCE_OIMFI | MX | Mexico |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | IDMX_DI_SOURCE_OIMFI | 0 | HLA0009203 | Accounts Receivable |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20090325 |
| SAP Release Created in | 600 |
