Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-AB (Application Component) Agency Business (Global Trade)⤷
WZRE_XI_PROXY (Package) Agency Business: SOA proxy implementations
IMG Activity
| ID | WLF_SOA_B2B_MAP_0001 | Basic Settings for Determining Default Data in Mapping |
| Transaction Code | S_EBS_44000199 | (empty) |
| Created on | 20101111 | |
| Customizing Attributes | WLF_SOA_B2B_INB_0001 | BAdI: Enhancements for InvoiceRequest_In |
| Customizing Activity | WLF_SOA_B2B_MAP_0001 | Basic Settings for Determining Default Data in Mapping |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | WLF_SOA_B2B_MAP_0001 |
Use
In this activity, you can make central settings necessary for processing the B2B Enterprise Services InvoiceRequest_In or InvoiceREquest_Out_V1 within the Agency Business application.
- Identification Scheme:
You use the identification scheme to define an identification number for your own company. You can create your own internal number or a standardized number, for example, an International Location Number /ILN). For a standard number, you must also specify an identification for the organization that allocated this standardized number. You can define precisely one identification scheme as a default.
- Default Organizational Units:
Here, you can process various sales-side and purchasing-side organizational units not included in B2B report InvoiceRequest, but that are essential for creating Agency Business documents. The selected organizational units must be assigned to the previously-selected company code.
- Proxy Mapping Groups for Pooled Payment:
The proxy mapping group bundles all default data necessary for processing an InvoiceRequest message. General data such as the company code, method of settlement, and, optionally, invoicing type must de defined. Additionally, an ID for the default organizational units and the ID of an identification scheme can be specified. As an alternative to the default ID for the default organizational units, the indicator for dynamic determination of the organizational units can be selected at runtime.
- Assigning a Proxy Mapping Group and an Identification Scheme to a Use
A proxy mapping group and an identification scheme can be defined for a use.
- Using Settings in Enterprise Service InvoiceRequest_Out_V1
When sending an InvoiceRequest message via Enterprise Service InvoiceRequest_Out_V1, the standard ID is written in one or several party ID element, depending on the relevant use. The internal party ID is only used if the RCOMP field has not been edited in Customizing for the company code. Data is determined for the identification scheme that is assigned to the relevant use. Unless this is done, the default identification scheme is used.
- Using Settings in Enterprise Service InvoiceRequest_In
When processing an InvoiceRequest message via Enterprise Service InvoiceRequest_In, the proxy mapping group and the derived default data and assigned identification scheme are determined.
The standard ID and the internal party ID of the identification scheme are used to determine whether an inbound message is to be processed in the standard billing application or by the Agency Business application.
If the organizational units are to be determined dynamically at runtime, this data is determined from the vendor's or customer's master data.
Requirements
You have activated Business Function ISR_RET_AGENCY_5.
If you have already used Enterprise Service InvoiceRequest_In, you can migrate the Customizing data of maintenance views V_TMZR_PRX_GP_IV and V_TMZR_PRX_GP_CR when you first call the maintenance views above for the identification scheme, default organizational units, and proxy mapping group.
Standard settings
Activities
Example
You have defined an ILN number as standard number for your company in an identification scheme. Bexause the ILN number is assigned by the GS1 Organization, you must fill the StandardAgencyID field with the value 9 , which identifies the GS1 Organization in accordance with UN/EDIFACT Codelist DE 3055.
You have edited a method of settlement and a company code in a proxy mapping group and now want to assign a default ID for the organizational units to it. To do this, only those default IDs that match the company code and match the method of payment Customizing regarding the settlement partner can be used. If settlement is only on the vendor side, only default IDs for which exclusively the purchasing-side organizational units have been processed can be used. For settlement on the customer side, only the sales-side organizational units can be processed.. If the All Org Data indicator (settlement partner) is selected, no check occurs.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
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 |
| TMPRX_IDNT | S - Table (with text table) | SM30 | Definition of Identification Schemes | |||
| V_TMPRX_DEF | V - View | SM30 | Definition of Default Data for Organisational Units | |||
| V_TMPRX_MG_B | V - View | SM30 | Definition of Proxy Mapping Groups for Payment | |||
| V_TMPRX_DET | V - View | SM30 | Assignment of Proxy Mapping Group and Identification Schemes to Use Cases |
History
| Last changed by/on | SAP | 20101112 |
| SAP Release Created in | 606 |
