interface functional design vendors master data...

Interface Functional DesignVendors Master Data ECC MDM to Regional ECCs

Project Name: Project T

Team: IM – MDM

Document Owner

Document Owner(s) Project/Organisation Role

Barry Andersson MDM Technical lead

Version Control

Version Status Date Author Change Description

v0.001 Draft 29/07/2009 Sara Oliva New document

v0.002 Review 30/07/2009 Marko Trninic Functional review

v1.000 Final 05/09/2009 Sara Oliva Final version

v1.001 Final 16/09/2009 Sara Oliva Changes done to meet technicalteam requirements

v1.002 Final 16/09/2009 Sara Oliva Updated purchasing organizationlist

v1.003 Final 21/01/2010 Pieter Erasmus Updated BBB-EE Specifications

v1.004 Final 17/05/2010 Pieter Erasmus Customer Field rules

V1.005 Final 04/04/2011 Sindi Mhlongo Updated to include logic for alwayssending POrg data to targetsystem

V1.006 Final 18/07/2011 Sindi Mhlongo Updated to include logic forexcluding vendors marked fordeletion or blocked

V2.001 Review 20/04/2012 Asseria Magagula Update company codes to beadded in filters

V2.001 Review 20/04/2012 Riaan Oosthuizen Review updates

V2.004 Review 09/05/2012 Asseria Magagula Updated 12 company codesprovided by Garikai Mutasa

V2.005 Review 21/05/2012 Asseria Magagula Added company code 8181 in filtersas per Craig

Confidential and Proprietary of 44

Version Status Date Author Change Description

V2.006 Review 18/06/2012 Asseria Magagula Added 6 company codes asrequested by Maurie Swanepoel

V2.007 Review 17/08/2012 Asseria Magagula Add CR 55339 – Modify existingVendor enhancement(/BGT/MM_IDOC_EXTEND_CREMAS)

Approved By

Name Project / Organisation RoleVersionApproved

Sign-off Date

Asseria Magagula MDM Team V2.005 [Signature] 05/06/2012

Martin Cruces Integration Team V2.005 [Signature] [Date]

Document location

Please follow the link to get the document


Table of Contents

1 OBJECTIVE OF DOCUMENT................................................................................................5

1.1 OVERVIEW............................................................................................................................. 5

1.2 SCOPE.................................................................................................................................... 5

1.3 OUT OF SCOPE..................................................................................................................... 5

1.4 RELATED DOCUMENTS........................................................................................................5

2 DEVELOPMENT JUSTIFICATION.........................................................................................6

3 BUSINESS OBJECTIVE.........................................................................................................7

4 DETAILED FUNCTIONAL SPECIFICATION..........................................................................8

4.1 PROCESS DIAGRAM.............................................................................................................8

4.2 PROPOSED TRANSFER METHOD / PROGRAM.................................................................8

4.3 CENTRAL ECC MDM TO REGIONAL ECCS........................................................................8

4.4 SOURCE/TARGET DATA.......................................................................................................8

4.4.1 SOURCE FIELDS......................................................................................................10

4.4.2 TARGET FIELDS.......................................................................................................12

4.5 FOLDER STRUCTURE........................................................................................................15

NO FOLDER REQUIRED DIRECT DISTRIBUTION...............................................................15

4.6 SYSTEM INFORMATION......................................................................................................15

4.7 MAPPING SAP FIELDS TO SOURCE/TARGET FIELDS....................................................16

4.8 REPORTING.........................................................................................................................20

4.9 BACK - UP REQUIREMENT................................................................................................20

5 CUSTOMISING DETAIL.......................................................................................................21

5.1.1 VENDORS..................................................................................................................21

5.2 SOURCE SYSTEM CONFIGURATION................................................................................24

5.2.1 DISTRIBUTION MODEL............................................................................................24

5.2.2 CUSTOMER FIELD UPDATE RESTRICTION...........................................................25

5.2.3 CUSTOMISED FIELDS – BBBEE.............................................................................25

5.2.4 CUSTOMISED FIELDS – VENDOR CONTACTS......................................................26


5.2.5 SENDING OF THE VENDOR IBAN AND ADDRESS................................................26

5.2.5.1 SENDING OF THE VENDOR IBAN.................................................................................26

5.2.5.2 SENDING OF THE VENDOR ADDRESS.........................................................................27

5.2.6 SENDING OF ALL PORGS FOR KRED VENDORS.................................................27

5.2.7 EXCLUSION OF VENDORS THAT ARE BLOCKED OR MARKED FOR DELETION27

5.2.8 PARTNER PROFILE..................................................................................................28

5.2.9 CHANGE POINTERS.................................................................................................28

5.3 JOB SCHEDULING..............................................................................................................30

6 CONTINGENCY.................................................................................................................... 30

7 PROCESS AND OPERATIONAL CONSIDERATIONS........................................................30

8 ERROR HANDLING.............................................................................................................31

9 TESTING REQUIREMENTS.................................................................................................31

10 DESIGN CONSTRAINTS......................................................................................................32

10.1 OPEN ISSUES...................................................................................................................... 32

11 APPENDIX............................................................................................................................ 33

11.1 PURCHASE ORGANISATIONS PER REGION....................................................................33

11.2 CHECK CRITERIA................................................................................................................45


1 OBJECTIVE OF DOCUMENT

2 Overview

SAB Miller as part of its global strategy is intending to standardise all its back office operations. This standardisation implies going towards a common and central data management process in all back office data related in order to get a data alignment over the global landscape.

3 Scope

The scope of this document is the interface for vendors between the central SAP ECC system and the regionalSAP ECCs. This interface will send via ALE any vendor created or modified in the central ECC MDM system tothe regional ECC systems.

This FD will cover the following interfaces relating to Vendors:

Vendor Master Data: CREMAS Company Addresses: ADRMAS Vendor IBAN data: IBAN_SAVEREPLICA; IBAN_CREATE; IBAN_CHANGE

Note: This FD does not cover the distribution of vendors to SRM MDM Catalogue (there may be references forinformational purposes)

4 Out of Scope

N/A

5 Related Documents

Technical Design

Process Integration mapping document

Other documents Vendors repositoryParent relationship custom tableSupplier Risk Rating Custom table


6 DEVELOPMENT JUSTIFICATION

Functional Owner Riaan Oosthuizen

Date Requested

Date Required

Functional Analyst Asseria Magagula

Technical Analyst Margaret van Huyssteen/ Martin Cruces

Priority Medium (recommended)

Consequence of no Delivery Other

Description of Alternative Solution

Manual creation of the data in the systems

Why Alternative is not Acceptable

Other


7 BUSINESS OBJECTIVE

Interface ID M.G.ZZ.810.69178

Interface Description Vendor Distribution from Central ECC to SAP MDM and regional ECC

Interface Title Vendor Master Data ECC MDM to Reg.ECC

Interface Type Outbound

Region Global

Release Global Template

Functional Area Procurement

Initiating Process Vendor is created/changed in SAP ECC

Business Requirement Global synchronization of the Vendor Master data

Business Gaps N/A

Business Benefit

Development Complexity Simple

Dependencies This interface depends on the creation of the custom tables for supplier risk

Assumptions N/A

Performance Considerations It is not included in the frequency and peak times the possible massiveinitial update. This process should be initiated once and executed undercontrolled conditions as per possible performance issues in the ALEdistribution.

Transaction Volume Globally 250-500 changes per dayGlobal massive changes: 1000-2500 per day (when required)

Frequency and Timing PEAK 100 p/hour

Processing Type Asynchronous

Document Audits/Checks Completed by

Name of person who completes section 11


8 DETAILED FUNCTIONAL SPECIFICATION

This interface will execute the extraction of vendor master data from the Global ECC the regional ECCs throughALE

9 Process Diagram

10 Proposed Transfer Method / Program

11 Central ECC MDM to regional ECCs

Vendor master data; company addresses and vendor IBAN data is maintained in the global ECC MDM client and distributed via ALE to the regional ECC systems (EU/LA; SA and HCM for IBAN master data).

12 Source/Target DataConfidential and Proprietary of 44

For distribution between ECCs, it will be done via direct mapping – which is standard to the IDOC distributionfunctionality.

13 Source fields

Field ID. File Name/Table Field Name Field Description Type Size

E1LFA1M-LIFNR LIFNR Account Number of Vendor or Creditor CHAR 10

E1LFA1M-BEGRU BEGRU Authorization Group CHAR 4

E1LFA1M-KTOKK KTOKK Vendor account group CHAR 4 E1LFA1M-LOEVM LOEVM Central Deletion Flag for Master Record CHAR 1

E1LFA1M-NAME1 NAME1 Employee's last name CHAR 35



E1LFA1M-ORT01 ORT01 City CHAR 35

E1LFA1M-SPERR SPERR Central posting block CHAR 1

E1LFA1M-SPERM SPERM Centrally imposed purchasing block CHAR 1

E1LFA1M-STKZU STKZU Liable for VAT CHAR 1

E1LFA1M-STRAS STRAS House number and street CHAR 35

E1LFA1M-TELF1 TELF1 First telephone number CHAR 16

E1LFA1M-VBUND VBUND Company ID of trading partner CHAR 6

E1LFA1M-STCEG STCEG VAT Registration Number CHAR 20

E1LFA1M-STKZN STKZN Natural Person CHAR 1

E1LFA1M-SPERQ SPERQ Function That Will Be Blocked CHAR 2

E1LFA1M-GBORT GBORT Place of birth of the person subject to withholding tax CHAR 25

E1LFA1M-GBDAT GBDAT Character field, 8 characters long CHAR 8

E1LFA1M-SEXKZ SEXKZKey for the Sex of the Person Subject to Withholding Tax CHAR 1

E1LFA1M-PROFS PROFS Profession CHAR 30

E1LFA1M-NODEL NODEL Central Deletion Block for Master Record CHAR 1

E1LFA1M-KUNNR KUNNR Customer CHAR 10

E1LFB1M-LIFNR LIFNR Account Number of Vendor or Creditor CHAR 10

E1LFB1M-BUKRS BUKRS Company code CHAR 6

E1LFB1M-SPERR SPERR Posting block for company code CHAR 1

E1LFB1M-LOEVM LOEVMDeletion Flag for Master Record (Company Code Level) CHAR 1

E1LFB1M-ZUAWA ZUAWA Key for sorting according to assignment numbers CHAR 3

E1LFB1M-AKONT AKONT Reconciliation Account in General Ledger CHAR 10

E1LFB1M-BEGRU BEGRU Authorization Group CHAR 4

E1LFB1M-ZWELS ZWELS List of the Payment Methods to be Considered CHAR 10

E1LFB1M-XVERR XVERR Indicator: Clearing between customer and vendor? CHAR 1

E1LFB1M-ZAHLS ZAHLS Block key for payment CHAR 1

E1LFB1M-ZTERM ZTERM Terms of Payment Key CHAR 4

E1LFB1M-EIKTO EIKTOShipper's (Our) Account Number at the Customer or Vendor CHAR 12

E1LFB1M-ZSABE ZSABE Clerk at vendor CHAR 15

E1LFB1M-BUSAB BUSAB Accounting clerk CHAR 2 E1LFB1M-LNRZB LNRZB Account number of the alternative payee CHAR 10 E1LFB1M-REPRF REPRF Check Flag for Double Invoices or Credit Memos CHAR 1

E1LFB1M-HBKID HBKID Short Key for a House Bank CHAR 5

E1LFB1M-XPORE XPORE Indicator: Pay all items separately ? CHAR 1



E1LFB1M-QSZNR QSZNR Character Field Length = 10 CHAR 10

E1LFB1M-QSZDT QSZDT Character field, 8 characters long CHAR 8

E1LFB1M-QSSKZ QSSKZ Withholding Tax Code CHAR 2

E1LFB1M-ALTKN ALTKN Previous Master Record Number CHAR 10

E1LFB1M-QLAND QLAND Withholding Tax Country Key CHAR 3

E1LFB1M-XEDIP XEDIP Indicator: Send Payment Advices by EDI CHAR 1

E1LFB1M-TLFXS TLFXS Accounting clerk's fax number at the customer/vendor CHAR 31

E1LFB1M-INTAD INTAD Internet address of partner company clerk CHAR 130

E1LFB1M-NODEL NODEL Central Deletion Block for Master Record CHAR 1

E1LFB1M-TLFNS TLFNSAccounting clerk's telephone number at business partner CHAR 30

E1LFB1M-MINDK MINDK Minority Indicator CHAR 3

E1LFM1M-LIFNR LIFNR Vendor Account Number CHAR 10

E1LFM1M-EKORG EKORG Character field of length 6 CHAR 6

E1LFM1M-SPERM SPERM Purchasing block at purchasing organization level CHAR 1

E1LFM1M-LOEVM LOEVM Delete flag for vendor at purchasing level CHAR 1

E1LFM1M-LFABC LFABC ABC indicator CHAR 1

E1LFM1M-WAERS WAERS R/2 table CHAR 5 E1LFM1M-VERKF VERKF Responsible Salesperson at Vendor's Office CHAR 30

E1LFM1M-TELF1 TELF1 Vendor's telephone number CHAR 16

E1LFM1M-ZTERM ZTERM Terms of Payment Key CHAR 4

E1LFM1M-INCO1 INCO1 Incoterms (Part 1) CHAR 3


E1LFM1M-WEBRE WEBRE Indicator: GR-Based Invoice Verification CHAR 1

E1LFM1M-KZABS KZABS Order Acknowledgment Requirement CHAR 1

E1LFM1M-KZAUT KZAUT Character field of length 1 CHAR 1

E1LFM1M-EXPVZ EXPVZ Mode of Transport for Foreign Trade CHAR 1

E1LFM1M-ZOLLA ZOLLA Customs Office: Office of Exit/Entry for Foreign Trade CHAR 6

E1LFM1M-EKGRP EKGRP Purchasing Group CHAR 3

E1LFM1M-XERSY XERSY Evaluated Receipt Settlement (ERS) CHAR 1

E1LFM1M-PLIFZ PLIFZ R/2 table CHAR 5

E1LFM1M-PRFRE PRFREIndicator: "relev. to price determination (vend. hierarchy) CHAR 1

E1LFM1M-NRGEW NRGEW Indicator whether discount in kind granted CHAR 1

E1LFM1M-BLIND BLINDIndicator: Doc. index compilation active for purchase orders CHAR 1

E1LFM1M-KZRET KZRET Indicates whether vendor is returns vendor CHAR 1

E1LFM1M-SKRIT SKRIT Vendor sort criterion for materials CHAR 1

E1LFM1M-XERSR XERSR Automatic evaluated receipt settlement for return items CHAR 1

E1LFM1M-EIKTO EIKTO Our account number with the vendor CHAR 12

E1LFM1M-PAPRF PAPRF Profile for transferring material data via IDoc PROACT CHAR 4

E1LFM1M-LEBRE LEBRE Indicator for service-based invoice verification CHAR 1

E1LFA1M-LNRZA LIFNR Account number of the alternative payee CHAR 10

E1BPAD1VL-PO_BOX PO_BOX PO_Box CHAR 10

E1BPAD1VL-PO_BOX_REG PO_BOX_REG Region_for_PO_Box CHAR 3

E1BPAD1VL-STREET STREET Street CHAR 60

E1BPAD1VL-STR_SUPPL1 STR_SUPPL1 Street_2 CHAR 40



E1BPAD1VL-STR_SUPPL2 STR_SUPPL2 Street_3 CHAR 40E1BPAD1VL-STR_SUPPL3 STR_SUPPL3 Street_4 CHAR 40E1BPAD1VL-LOCATION LOCATION Street_5 CHAR 40

E1BPAD1VL-COUNTRY COUNTRY Country CHAR 3

E1BPAD1VL-LANGU LANGU Language CHAR 1

E1BPAD1VL-REGION REGION Region CHAR 3

E1BPAD1VL-SORT1 SORT1 Search_Term_1 CHAR 20


E1LFBKM-BANKS BANKS Country CHAR 3

E1LFBKM-BANKL BANKL Bank Key CHAR 15

E1LFBKM-BANKN BANKN Bank Account Number CHAR 18

E1LFBKM-BANKA BANKA Bank Name CHAR 60

E1LFBKM-SWIFT SWIFT Swift Code CHAR 11

E1LFBKM-BNKLZ BNKLZ Bank Number CHAR 15

E1LFBKM-BRNCH BRNCH Bank Branch CHAR 40

E1LFBKM-KOINH KOINH Account Holder CHAR 60

E1LFBKM-IBAN IBAN IBAN CHAR 34

E1LFA1M-ANRED TITLE Title CHAR 4

E1BPAD1VL-CITY CITY City CHAR 40

E1BPAD1VL-DISTRICT DISTRICT District CHAR 40

E1BPAD1VL-POSTL_COD1 POSTL_COD1 City_Postal_Code CHAR 10

E1BPAD1VL-POSTL_COD2 POSTL_COD2 PO_Box_Postal_Code CHAR 10

E1BPAD1VL-POSTL_COD3 POSTL_COD3 Company_Postal_Code CHAR 10

E1BPAD1VL-PO_BOX_CIT PO_BOX_CIT City_PO_Box_Code CHAR 40

E1BPAD1VL-COMM_TYPE COMM_TYPE Standard Communication Method CHAR 3

E1BPADTEL-TELEPHONE TELEPHONE Phone_Number CHAR 1

E1BPADFAX-FAX FAX Fax_Number CHAR 1

E1BPADSMTP-E_MAIL E_MAIL E_Mail CHAR 1

14 Target fields


E1LFA1M-LIFNR LIFNR Account Number of Vendor or Creditor CHAR 10

E1LFA1M-BEGRU BEGRU Authorization Group CHAR 4

E1LFA1M-KTOKK KTOKK Vendor account group CHAR 4 E1LFA1M-LOEVM LOEVM Central Deletion Flag for Master Record CHAR 1




E1LFA1M-ORT01 ORT01 City CHAR 35

E1LFA1M-SPERR SPERR Central posting block CHAR 1

E1LFA1M-SPERM SPERM Centrally imposed purchasing block CHAR 1

E1LFA1M-STKZU STKZU Liable for VAT CHAR 1

E1LFA1M-STRAS STRAS House number and street CHAR 35

E1LFA1M-TELF1 TELF1 First telephone number CHAR 16

E1LFA1M-VBUND VBUND Company ID of trading partner CHAR 6

E1LFA1M-STCEG STCEG VAT Registration Number CHAR 20

E1LFA1M-STKZN STKZN Natural Person CHAR 1

E1LFA1M-SPERQ SPERQ Function That Will Be Blocked CHAR 2

E1LFA1M-GBORT GBORT Place of birth of the person subject to withholding tax CHAR 25



E1LFA1M-GBDAT GBDAT Character field, 8 characters long CHAR 8

E1LFA1M-SEXKZ SEXKZKey for the Sex of the Person Subject to Withholding Tax CHAR 1

E1LFA1M-PROFS PROFS Profession CHAR 30

E1LFA1M-NODEL NODEL Central Deletion Block for Master Record CHAR 1

E1LFA1M-KUNNR KUNNR Customer CHAR 10

E1LFB1M-LIFNR LIFNR Account Number of Vendor or Creditor CHAR 10

E1LFB1M-BUKRS BUKRS Company code CHAR 6

E1LFB1M-SPERR SPERR Posting block for company code CHAR 1

E1LFB1M-LOEVM LOEVMDeletion Flag for Master Record (Company Code Level) CHAR 1

E1LFB1M-ZUAWA ZUAWA Key for sorting according to assignment numbers CHAR 3

E1LFB1M-AKONT AKONT Reconciliation Account in General Ledger CHAR 10

E1LFB1M-BEGRU BEGRU Authorization Group CHAR 4

E1LFB1M-ZWELS ZWELS List of the Payment Methods to be Considered CHAR 10

E1LFB1M-XVERR XVERR Indicator: Clearing between customer and vendor? CHAR 1

E1LFB1M-ZAHLS ZAHLS Block key for payment CHAR 1

E1LFB1M-ZTERM ZTERM Terms of Payment Key CHAR 4

E1LFB1M-EIKTO EIKTOShipper's (Our) Account Number at the Customer or Vendor CHAR 12

E1LFB1M-ZSABE ZSABE Clerk at vendor CHAR 15

E1LFB1M-BUSAB BUSAB Accounting clerk CHAR 2 E1LFB1M-LNRZB LNRZB Account number of the alternative payee CHAR 10 E1LFB1M-REPRF REPRF Check Flag for Double Invoices or Credit Memos CHAR 1

E1LFB1M-HBKID HBKID Short Key for a House Bank CHAR 5

E1LFB1M-XPORE XPORE Indicator: Pay all items separately ? CHAR 1

E1LFB1M-QSZNR QSZNR Character Field Length = 10 CHAR 10

E1LFB1M-QSZDT QSZDT Character field, 8 characters long CHAR 8

E1LFB1M-QSSKZ QSSKZ Withholding Tax Code CHAR 2

E1LFB1M-ALTKN ALTKN Previous Master Record Number CHAR 10

E1LFB1M-QLAND QLAND Withholding Tax Country Key CHAR 3

E1LFB1M-XEDIP XEDIP Indicator: Send Payment Advices by EDI CHAR 1

E1LFB1M-TLFXS TLFXS Accounting clerk's fax number at the customer/vendor CHAR 31

E1LFB1M-INTAD INTAD Internet address of partner company clerk CHAR 130

E1LFB1M-NODEL NODEL Central Deletion Block for Master Record CHAR 1

E1LFB1M-TLFNS TLFNSAccounting clerk's telephone number at business partner CHAR 30

E1LFB1M-MINDK MINDK Minority Indicator CHAR 3

E1LFM1M-LIFNR LIFNR Vendor Account Number CHAR 10

E1LFM1M-EKORG EKORG Character field of length 6 CHAR 6

E1LFM1M-SPERM SPERM Purchasing block at purchasing organization level CHAR 1

E1LFM1M-LOEVM LOEVM Delete flag for vendor at purchasing level CHAR 1

E1LFM1M-LFABC LFABC ABC indicator CHAR 1

E1LFM1M-WAERS WAERS R/2 table CHAR 5 E1LFM1M-VERKF VERKF Responsible Salesperson at Vendor's Office CHAR 30

E1LFM1M-TELF1 TELF1 Vendor's telephone number CHAR 16

E1LFM1M-ZTERM ZTERM Terms of Payment Key CHAR 4





E1LFM1M-WEBRE WEBRE Indicator: GR-Based Invoice Verification CHAR 1

E1LFM1M-KZABS KZABS Order Acknowledgment Requirement CHAR 1

E1LFM1M-KZAUT KZAUT Character field of length 1 CHAR 1

E1LFM1M-EXPVZ EXPVZ Mode of Transport for Foreign Trade CHAR 1

E1LFM1M-ZOLLA ZOLLA Customs Office: Office of Exit/Entry for Foreign Trade CHAR 6

E1LFM1M-EKGRP EKGRP Purchasing Group CHAR 3

E1LFM1M-XERSY XERSY Evaluated Receipt Settlement (ERS) CHAR 1

E1LFM1M-PLIFZ PLIFZ R/2 table CHAR 5

E1LFM1M-PRFRE PRFREIndicator: "relev. to price determination (vend. hierarchy) CHAR 1

E1LFM1M-NRGEW NRGEW Indicator whether discount in kind granted CHAR 1

E1LFM1M-BLIND BLINDIndicator: Doc. index compilation active for purchase orders CHAR 1

E1LFM1M-KZRET KZRET Indicates whether vendor is returns vendor CHAR 1

E1LFM1M-SKRIT SKRIT Vendor sort criterion for materials CHAR 1

E1LFM1M-XERSR XERSR Automatic evaluated receipt settlement for return items CHAR 1

E1LFM1M-EIKTO EIKTO Our account number with the vendor CHAR 12

E1LFM1M-PAPRF PAPRF Profile for transferring material data via IDoc PROACT CHAR 4

E1LFM1M-LEBRE LEBRE Indicator for service-based invoice verification CHAR 1

E1LFA1M-LNRZA LIFNR Account number of the alternative payee CHAR 10

E1BPAD1VL-PO_BOX PO_BOX PO_Box CHAR 10

E1BPAD1VL-PO_BOX_REG PO_BOX_REG Region_for_PO_Box CHAR 3

E1BPAD1VL-STREET STREET Street CHAR 60

E1BPAD1VL-STR_SUPPL1 STR_SUPPL1 Street_2 CHAR 40E1BPAD1VL-STR_SUPPL2 STR_SUPPL2 Street_3 CHAR 40E1BPAD1VL-STR_SUPPL3 STR_SUPPL3 Street_4 CHAR 40E1BPAD1VL-LOCATION LOCATION Street_5 CHAR 40

E1BPAD1VL-COUNTRY COUNTRY Country CHAR 3

E1BPAD1VL-LANGU LANGU Language CHAR 1

E1BPAD1VL-REGION REGION Region CHAR 3



E1LFBKM-BANKS BANKS Country CHAR 3

E1LFBKM-BANKL BANKL Bank Key CHAR 15

E1LFBKM-BANKN BANKN Bank Account Number CHAR 18

E1LFBKM-BANKA BANKA Bank Name CHAR 60

E1LFBKM-SWIFT SWIFT Swift Code CHAR 11

E1LFBKM-BNKLZ BNKLZ Bank Number CHAR 15

E1LFBKM-BRNCH BRNCH Bank Branch CHAR 40

E1LFBKM-KOINH KOINH Account Holder CHAR 60

E1LFBKM-IBAN IBAN IBAN CHAR 34

E1LFA1M-ANRED TITLE Title CHAR 4

E1BPAD1VL-CITY CITY City CHAR 40

E1BPAD1VL-DISTRICT DISTRICT District CHAR 40

E1BPAD1VL-POSTL_COD1 POSTL_COD1 City_Postal_Code CHAR 10

E1BPAD1VL-POSTL_COD2 POSTL_COD2 PO_Box_Postal_Code CHAR 10

E1BPAD1VL-POSTL_COD3 POSTL_COD3 Company_Postal_Code CHAR 10

E1BPAD1VL-PO_BOX_CIT PO_BOX_CIT City_PO_Box_Code CHAR 40



E1BPAD1VL-COMM_TYPE COMM_TYPE Standard Communication Method CHAR 3

E1BPADTEL-TELEPHONE TELEPHONE Phone_Number CHAR 1

E1BPADFAX-FAX FAX Fax_Number CHAR 1

E1BPADSMTP-E_MAIL E_MAIL E_Mail CHAR 1

15 Folder Structure

No folder required direct distribution.

16 System Information

Sending System

System Name CENTRAL SAP ECC (GP7)

System Technology R3

File Type Sent IDOC

Middleware System

System Name NO MIDDLEWARE RFC CONNECTIONS

System Technology RFC Connection

Additional Information

Receiving System

System NameSAP Regional ECC (LatAm EP7, Europe EP7, Africa & Asia BP1, HCM forIBAN data)

System Technology Technology Type

SAP R3

File Type Received IDOC


17 Mapping SAP Fields to Source/Target Fields

Direct mapping applicable, as the interface will be a 1:1 mapping from the IDoc to the XML file / IDoc and therewill not be any transformation in SAP ECC.

SAP Tablename

SAP Field name (functional) SAP Fieldname

(technical)

SAPField

length

SAPfieldtype

Mandatory TargetFieldName

TargetField

length

TargetFieldtype

Mappingdetails

LFA1Account Number of Vendor or Creditor LIFNR 10 CHAR LIFNR 10 CHAR Direct Mapping

LFA1 Authorization Group BEGRU 4 CHAR BEGRU 4 CHAR Direct Mapping

LFA1 Vendor account group KTOKK 4 CHAR KTOKK 4 CHAR Direct Mapping

LFA1Central Deletion Flag for MasterRecord LOEVM 1 CHAR LOEVM 1 CHAR Direct Mapping

LFA1 Employee's last name NAME1 35 CHAR NAME1 35 CHAR Direct Mapping



BNKA City ORT01 35 CHAR ORT01 35 CHAR Direct Mapping

LFA1 Central posting block SPERR 1 CHAR SPERR 1 CHAR Direct Mapping

LFA1Centrally imposed purchasing block SPERM 1 CHAR SPERM 1 CHAR Direct Mapping

LFA1 Liable for VAT STKZU 1 CHAR STKZU 1 CHAR Direct Mapping

ADRC House number and street STRAS 35 CHAR STRAS 35 CHAR Direct Mapping

ADRC First telephone number TELF1 16 CHAR TELF1 16 CHAR Direct Mapping

LFA1 Company ID of trading partner VBUND 6 CHAR VBUND 6 CHAR Direct Mapping

LFA1 VAT Registration Number STCEG 20 CHAR STCEG 20 CHAR Direct Mapping

LFA1 Natural Person STKZN 1 CHAR STKZN 1 CHAR Direct Mapping

LFA1 Function That Will Be Blocked SPERQ 2 CHAR SPERQ 2 CHAR Direct Mapping

LFA1Place of birth of the person subject to withholding tax GBORT 25 CHAR GBORT 25 CHAR Direct Mapping

LFA1Character field, 8 characters long GBDAT 8 CHAR GBDAT 8 CHAR Direct Mapping

LFA1Key for the Sex of the Person Subject to Withholding Tax SEXKZ 1 CHAR SEXKZ 1 CHAR Direct Mapping

LFA1 Profession PROFS 30 CHAR PROFS 30 CHAR Direct Mapping

LFA1Central Deletion Block for Master Record NODEL 1 CHAR NODEL 1 CHAR Direct Mapping

LFB1Account Number of Vendor or Creditor LIFNR 10 CHAR LIFNR 10 CHAR Direct Mapping

LFB1 Character field of length 6 BUKRS 6 CHAR BUKRS 6 CHAR Direct Mapping

LFA1 Posting block for company code SPERR 1 CHAR SPERR 1 CHAR Direct Mapping

LFA1Deletion Flag for Master Record(Company Code Level) LOEVM 1 CHAR LOEVM 1 CHAR Direct Mapping

LFB1Key for sorting according to assignment numbers ZUAWA 3 CHAR ZUAWA 3 CHAR Direct Mapping

LFB1Reconciliation Account in General Ledger AKONT 10 CHAR AKONT 10 CHAR Direct Mapping

LFA1 Authorization Group BEGRU 4 CHAR BEGRU 4 CHAR Direct Mapping

LFB1List of the Payment Methods to be Considered ZWELS 10 CHAR ZWELS 10 CHAR Direct Mapping

LFB1Indicator: Clearing between customer and vendor? XVERR 1 CHAR XVERR 1 CHAR Direct Mapping

LFB1 Block key for payment ZAHLS 1 CHAR ZAHLS 1 CHAR Direct Mapping

LFB1 Terms of Payment Key ZTERM 4 CHAR ZTERM 4 CHAR Direct MappingLFB1 Shipper's (Our) Account EIKTO 12 CHAR EIKTO 12 CHAR Direct Mapping


SAP Tablename


(technical)

SAPField

length

SAPfieldtype


TargetField

length

TargetFieldtype

Mappingdetails

Number at the Customer or Vendor

LFB1 Clerk at vendor ZSABE 15 CHAR ZSABE 15 CHAR Direct Mapping

LFB1 Accounting clerk BUSAB 2 CHAR BUSAB 2 CHAR Direct Mapping

LFB1Account number of the alternative payee LNRZB 10 CHAR LNRZB 10 CHAR Direct Mapping

LFB1Check Flag for Double Invoices or Credit Memos REPRF 1 CHAR REPRF 1 CHAR Direct Mapping

LFB1 Short Key for a House Bank HBKID 5 CHAR HBKID 5 CHAR Direct Mapping

LFB1Indicator: Pay all items separately ? XPORE 1 CHAR XPORE 1 CHAR Direct Mapping

LFB1 Character Field Length = 10 QSZNR 10 CHAR QSZNR 10 CHAR Direct Mapping

LFB1Character field, 8 characters long QSZDT 8 CHAR QSZDT 8 CHAR Direct Mapping

LFB1 Withholding Tax Code QSSKZ 2 CHAR QSSKZ 2 CHAR Direct Mapping

LFB1Previous Master Record Number ALTKN 10 CHAR ALTKN 10 CHAR Direct Mapping

LFB1 Withholding Tax Country Key QLAND 3 CHAR QLAND 3 CHAR Direct Mapping

LFB1Indicator: Send Payment Advices by EDI XEDIP 1 CHAR XEDIP 1 CHAR Direct Mapping

LFB1Accounting clerk's fax number at the customer/vendor TLFXS 31 CHAR TLFXS 31 CHAR Direct Mapping

LFB1Internet address of partner company clerk INTAD 130 CHAR INTAD 130 CHAR Direct Mapping

LFB1Central Deletion Block for Master Record NODEL 1 CHAR NODEL 1 CHAR Direct Mapping

LFB1Accounting clerk's telephone number at business partner TLFNS 30 CHAR TLFNS 30 CHAR Direct Mapping

LFB1 Vendor Account Number LIFNR 10 CHAR LIFNR 10 CHAR Direct Mapping

LFB1 Minority Indicator MINDK 3 CHAR MINDK 3 CHAR Direct Mapping

LFM1 Character field of length 6 EKORG 6 CHAR EKORG 6 CHAR Direct Mapping

LFM1Purchasing block at purchasing organization level SPERM 1 CHAR SPERM 1 CHAR Direct Mapping

LFM1Delete flag for vendor at purchasing level LOEVM 1 CHAR LOEVM 1 CHAR Direct Mapping

LFM1 ABC indicator LFABC 1 CHAR LFABC 1 CHAR Direct Mapping

LFM1 R/2 table WAERS 5 CHAR WAERS 5 CHAR Direct Mapping

LFM1Responsible Salesperson at Vendor's Office VERKF 30 CHAR VERKF 30 CHAR Direct Mapping

LFM1 Vendor's telephone number TELF1 16 CHAR TELF1 16 CHAR Direct Mapping

LFM1 Terms of Payment Key ZTERM 4 CHAR ZTERM 4 CHAR Direct Mapping

LFM1 Incoterms (Part 1) INCO1 3 CHAR INCO1 3 CHAR Direct Mapping

LFM1 Incoterms (Part 2) INCO2 28 CHAR INCO2 28 CHAR Direct Mapping

LFM1Indicator: GR-Based Invoice Verification WEBRE 1 CHAR WEBRE 1 CHAR Direct Mapping

LFM1Order Acknowledgment Requirement KZABS 1 CHAR KZABS 1 CHAR Direct Mapping

LFM1 Character field of length 1 KZAUT 1 CHAR KZAUT 1 CHAR Direct Mapping

LFM1Mode of Transport for Foreign Trade EXPVZ 1 CHAR EXPVZ 1 CHAR Direct Mapping

LFM1Customs Office: Office of Exit/Entry for Foreign Trade ZOLLA 6 CHAR ZOLLA 6 CHAR Direct Mapping

LFM1 Purchasing Group EKGRP 3 CHAR EKGRP 3 CHAR Direct Mapping

LFM1Evaluated Receipt Settlement (ERS) XERSY 1 CHAR XERSY 1 CHAR Direct Mapping

LFM1 R/2 table PLIFZ 5 CHAR PLIFZ 5 CHAR Direct Mapping


SAP Tablename


(technical)

SAPField

length

SAPfieldtype


TargetField

length

TargetFieldtype

Mappingdetails

LFM1Indicator: "relev. to price determination (vend. hierarchy) PRFRE 1 CHAR PRFRE 1 CHAR Direct Mapping

LFM1Indicator whether discount in kind granted NRGEW 1 CHAR NRGEW 1 CHAR Direct Mapping

LFM1

Indicator: Doc. index compilation active for purchase orders BLIND 1 CHAR BLIND 1 CHAR Direct Mapping

LFM1Indicates whether vendor is returns vendor KZRET 1 CHAR KZRET 1 CHAR Direct Mapping

LFM1Vendor sort criterion for materials SKRIT 1 CHAR SKRIT 1 CHAR Direct Mapping

LFM1Automatic evaluated receipt settlement for return items XERSR 1 CHAR XERSR 1 CHAR Direct Mapping

LFM1Our account number with the vendor EIKTO 12 CHAR EIKTO 12 CHAR Direct Mapping

LFM1Profile for transferring material data via IDoc PROACT PAPRF 4 CHAR PAPRF 4 CHAR Direct Mapping

LFM1Indicator for service-based invoice verification LEBRE 1 CHAR LEBRE 1 CHAR Direct Mapping

LFM1Account number of the alternative payee LIFNR 10 CHAR LIFNR 10 CHAR Direct Mapping

LFA1 PO_Box PO_BOX 10 CHAR PO_BOX 10 CHAR Direct Mapping

LFA1 Region_for_PO_Box PO_BOX_REG 3 CHAR

PO_BOX_REG 3 CHAR Direct Mapping

LFA1 Street STREET 60 CHAR STREET 60 CHAR Direct Mapping

LFA1 Street_2 STR_SUPPL1 40 CHAR

STR_SUPPL1 40 CHAR Direct Mapping

LFA1 Street_3STR_SUPPL2 40 CHAR


LFA1 Street_4 STR_SUPPL3 40 CHAR


LFA1 Street_5 LOCATION 40 CHAR LOCATION 40 CHAR Direct Mapping

LFA1 Country COUNTRY 3 CHAR COUNTRY 3 CHAR Direct Mapping

LFA1 Language LANGU 1 CHAR LANGU 1 CHAR Direct Mapping

LFA1 Region REGION 3 CHAR REGION 3 CHAR Direct Mapping

LFA1 Search_Term_1 SORT1 20 CHAR SORT1 20 CHAR Direct Mapping

LFA1 Search_Term_2 SORT2 20 CHAR SORT2 20 CHAR Direct Mapping

LFA1 Customer KUNNR 10 CHAR KUNNR 10 CHAR

Sending Restricted according Rule in Section 5.1.2

BNKA Country BANKS 3 CHAR BANKS 3 CHAR Direct Mapping

BNKA Bank Key BANKL 15 CHAR BANKL 15 CHAR Direct Mapping

LFBK Bank Account Number BANKN 18 CHAR BANKN 18 CHAR Direct Mapping

BNKA Bank Name BANKA 60 CHAR BANKA 60 CHAR Direct Mapping

BNKA Swift Code SWIFT 11 CHAR SWIFT 11 CHAR Direct Mapping

BNKA Bank Number BNKLZ 15 CHAR BNKLZ 15 CHAR Direct Mapping

BNKA Bank Branch BRNCH 40 CHAR BRNCH 40 CHAR Direct Mapping

LFBK Account Holder KOINH 60 CHAR KOINH 60 CHAR Direct Mapping

TIBAN IBAN IBAN 34 CHAR IBAN 34 CHAR Direct Mapping

LFA1 Title TITLE 4 CHAR TITLE 4 CHAR Direct Mapping

LFA1 City CITY 40 CHAR CITY 40 CHAR Direct Mapping

LFA1 District DISTRICT 40 CHAR DISTRICT 40 CHAR Direct Mapping

LFA1 City_Postal_Code POSTL_CO 10 CHAR POSTL_ 10 CHAR Direct Mapping


SAP Tablename


(technical)

SAPField

length

SAPfieldtype


TargetField

length

TargetFieldtype

Mappingdetails

D1 COD1

LFA1 PO_Box_Postal_Code POSTL_COD2 10 CHAR

POSTL_COD2 10 CHAR Direct Mapping

LFA1 Company_Postal_Code POSTL_COD3 10 CHAR

POSTL_COD3 10 CHAR Direct Mapping

ADRC City_PO_Box_Code PO_BOX_CIT 40 CHAR

PO_BOX_CIT 40 CHAR Direct Mapping

ADRCStandard Communication Method

COMM_TYPE 3 CHAR

COMM_TYPE 3 CHAR Direct Mapping

LFA1 Phone_NumberTELEPHONE 1 CHAR

TELEPHONE 1 CHAR Direct Mapping

LFA1 Fax_Number STD_NO 1 CHAR STD_NO 1 CHAR Direct Mapping

LFA1 E_Mail STD_NO 1 CHAR STD_NO 1 CHAR Direct Mapping/BSA/TA_VNDPOIN1 Date from BEGDT 8 CHAR BEGDT 8 CHAR Direct Mapping/BSA/TA_VNDPOIN1 Reference vendor name NAME 35 CHAR NAME 35 CHAR Direct Mapping/BSA/TA_VNDPOIN1 DTI Class DTICLS 10 CHAR DTICLS 10 CHAR Direct Mapping/BSA/TA_VNDPOIN1 Recipient ED REC_ED 1 CHAR REC_ED 1 CHAR Direct Mapping/BSA/TA_VNDPOIN1

Enterprise Development Candidate EDC 3 CHAR EDC 3 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Value Add VAL_ADD 1 CHAR

VAL_ADD 1 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 >= 50.1% black owned

BLACK_OWN 1 CHAR

BLACK_OWN 1 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 >= 30% Black women owned

BLACK_WOM 1 CHAR

BLACK_WOM 1 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 B2B BEE Level

/BSA/LEVEL 2 CHAR

/BSA/LEVEL 2 CHAR Direct Mapping

/BSA/TA_VNDPOIN1

B2B BEE Total Weighting Percentage

TOT_WEIGHTING 5 CHAR

TOT_WEIGHTING 5 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 VAT Registration Number STCEG 20 CHAR STCEG 20 CHAR Direct Mapping/BSA/TA_VNDPOIN1 New VAT registration number

/BSA/STCEG 20 CHAR

/BSA/STCEG 20 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Search Term 2 COMP_NO 20 CHAR

COMP_NO 20 CHAR Direct Mapping

/BSA/TA_VNDPOIN1

New company registration number

/BSA/COMP_NO 20 CHAR

/BSA/COMP_NO 20 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Comment

ZCOMMENT 250 CHAR

ZCOMMENT 250 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Rating Agency's Name

RATING_AGENCY 50 CHAR

RATING_AGENCY 50 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Score Card Link

SCORE_CARD_LINK 128 CHAR

SCORE_CARD_LINK 128 CHAR Direct Mapping


SAP Tablename


(technical)

SAPField

length

SAPfieldtype


TargetField

length

TargetFieldtype

Mappingdetails

/BSA/TA_VNDPOIN1 Lock and unlock status STATUS 5 CHAR STATUS 5 CHAR Direct Mapping/BGT/VEND_EMAIL Plant WERKS_D 4 CHAR

WERKS_D 4 CHAR Direct Mapping

/BGT/VEND_EMAIL

Responsible Salesperson at Vendor's Office EVERK 30 CHAR EVERK 30 CHAR Direct Mapping

/BGT/VEND_EMAIL E-Mail Address

AD_SMTPADR 241 CHAR

AD_SMTPADR 241 CHAR Direct Mapping

/BGT/VEND_EMAIL Fax Number TELFX 31 CHAR TELFX 31 CHAR Direct Mapping/BGT/VEND_EMAIL First telephone number TELF1 16 CHAR TELF1 16 CHAR Direct Mapping

18 Reporting

N/A

19 Back - up Requirement

N/A


20 CUSTOMISING DETAIL

The distribution model must be configured in transaction SALE in the path:

IDoc Interface Modelling and implementing Business Processes Maintain Distribution model and distributionviews.

The following message types need to be configured in the ALE distribution: CREMAS AddressOrg. SaveReplica (BAPI) IBAN.Change (BAPI) IBAN.Create (BAPI) IBAN. SaveReplica (BAPI)

Besides the standard distribution model configuration; there are requirements for enhancements on some ofabove mentioned message types.

21 Vendors

Message type Description System1 CREMAS IDOC Routing:

Vendors that are extended to purchase orgs and/or company codes shouldbe distributed to the relevant receiving systems – based on the filtersconfigured in the ALE distribution model. Basic views should not bedistributed if the vendor is not extended to a purchase org or company codeor not configured as per distribution model filters.

CR Release 2: At present, the basic data of vendors are distributed to bothEU/LA and SA. The distribution model filters non-relevant purchase Orgs andcompany codes and basic changes still go to all the connected receivers.

An enhancement is required to stop IDOC’s in the Sending system (ECCMDM) - if the vendors are not extended to purchasing Orgs or companycodes.

Sendingsystem –ECC MDM

2 CREMAS Send all Purchase Orgs and Company CodesSelect all LFM1(Purchase Orgs) and LFB1(Company Codes) records. - wrapped in Data Migration.(According to filter criteria these records will be filtered from the distributionmodel in BD64). It is required for SRM MDM Catalogue to have all extendedpurchase orgs for the vendor sent.)

Note: This functionality has already been implemented.


3.1 CREMAS IDOC Extension : BBBEE Data(/BGT/MMVENPOINTS):

Extend the standard CREMAS message type with additional fields for BBBEE data. This logic is only applicable for SA and the functionality checks the country code accordingly. This data is retrieved from custom table: /bsa/ta_vndpoin1:


(Processcustomsegment


/bgt/mmvenpoints-/bgt/de_begdt = gwa_vndpoin1-begdt. /bgt/mmvenpoints-/bgt/vname = gwa_vndpoin1-name. /bgt/mmvenpoints-/bgt/de_dticls = gwa_vndpoin1-dticls. /bgt/mmvenpoints-/bgt/rec_ed = gwa_vndpoin1-rec_ed. /bgt/mmvenpoints-/bgt/de_edc = gwa_vndpoin1-edc. /bgt/mmvenpoints-/bgt/val_add = gwa_vndpoin1-val_add. /bgt/mmvenpoints-/bgt/black_own = gwa_vndpoin1-black_own. /bgt/mmvenpoints-/bgt/black_wom = gwa_vndpoin1-black_wom. /bgt/mmvenpoints-/bgt/bee_level = gwa_vndpoin1-/bsa/level. /bgt/mmvenpoints-/bgt/tot_weight = gwa_vndpoin1-tot_weighting. /bgt/mmvenpoints-stceg = gwa_vndpoin1-stceg. /bgt/mmvenpoints-/bgt/stceg = gwa_vndpoin1-/bsa/stceg. /bgt/mmvenpoints-ad_sort2 = gwa_vndpoin1-comp_no. /bgt/mmvenpoints-/bgt/comp_no = gwa_vndpoin1-/bsa/comp_no. /bgt/mmvenpoints-/bgt/comment = gwa_vndpoin1-zcomment. /bgt/mmvenpoints-/bgt/rating_agcy = gwa_vndpoin1-rating_agency. /bgt/mmvenpoints-/bgt/score_card = gwa_vndpoin1-score_card_link.

This has already been implemented.

onreceivingsystem)

3.2 CREMAS IDOC Extension : Plant Contact data(/BGT/MMVENPOINTS1):

Extend the standard CREMAS message type with additional fields for plant contact data. This information is available on the custom view from SABGROUP and is applicable for both EU/LA and SA . This data is retrieved

from custom table: /bgt/vend_email: /bgt/mmvenpoints1-plant = gwa_vend_email-plant. /bgt/mmvenpoints1-sales_person = gwa_vend_email-sales_person.


(Processcustomsegmentonreceivingsystem)


/bgt/mmvenpoints1-email = gwa_vend_email-email. /bgt/mmvenpoints1-fax = gwa_vend_email-fax. /bgt/mmvenpoints1-telephone = gwa_vend_email-telephone.


3.3 CREMAS IDOC Extension : Plant Contact data(/BGT/MMVENPOINTS1):

Modify existing vendor enhancement (/BGT/MM_IDOC_EXTEND_CREMAS)to cater for deletions and updates of plant contact details. When the custom table for plant contact details are updated from Cransoft, the relevant insert/update/deletion should be transferred from SAP MDM to the Regional ECC system via the CREMAS IDoc. (Ref. CR 55339)


(Processcustomsegmentonreceivingsystem)

4 CREMAS Selective Updates:

Only overwrite customer field (KUNNR) for account groups containing “IC..Intercompany Vendors”. For all other account groups the customer field will never be overwritten by the CREMAS ALE.


Receivingsystems(EU/LAand SA)

5 CREMAS Blocked/Marked for deletion: (SRM Requirement – covered in SRM MDM catalogue FD)

Vendors that are marked for deletion or blocked – should not be distributed to the SRM MDM catalogue.

SendingsystemRegionalECC

6 CREMAS Custom filters : KRED Vendors (SRM Requirement – covered in SRM MDM catalogue FD)

Only KRED vendors to be distributed to SRM MDM CataloguesThis has already been implemented.

SendingsystemRegionalECC

7 ADRMAS IDOC Routing:Address data for Vendors that are extended to purchase orgs and/orcompany codes should be distributed to the relevant receiving systems. Thefiltering should be based on the purchase org and company code filters forthe Vendor ALE distribution model. Address data should not be distributed ifthe relevant vendor has not been extended to a purchase org or companycode.

CR Release 2: At present, address data for all vendors’ changes are beingdistributed to both EU/LA and SA. It is required to stop IDOC’s at source – ifthe relevant vendor has not been extended to a purchase org/ company codeor not configured for the particular vendor in the CREMAS distribution



model..

An enhancement is required to stop IDOC’s in the Sending system (ECCMDM) - if the relevant vendors are not extended to purchasing Orgs orcompany codes.

8 IBAN Vendor IBAN Data DistributionIBAN numbers are maintained on vendors (XK02) and is distributed viaseparate IDOC’s(IBAN_SAVEREPLICA; IBAN_CHANGE;IBAN_CREATE).This is a standard BAPI configuarion for sending IBAN datato the regional systems.


22 Source System configuration

23 Distribution model

Source and Target System Data Flow diagram

Detail


Model Name Sender Receiver Direction Message/Bapi FilterMDM ( MDM Distribution model)

LS for Central ECC LS for regional ECC (EU/LA and SA)

Outbound CREMAS Purchasing Orgs;Company Codes

MDM ( MDM Distribution model)

LS for Central ECC LS for regional ECC (EU/LA and SA)

Outbound ADRMAS.Savereplica(BAPI) None (custom logicto filter based on CREMAS distribution model).

MDM ( MDM Distribution model)

LS for Central ECC LS for regional ECC and global HCM (EU/LA and SA; HCM)

Outbound IBAN.SAvereplicaIBAN.ChangeIBAN.Create

None

In the transaction WE20 we must then configure partner profiles for the distribution configured in SALEtransaction if we haven’t used the automatic generation for partner profiles.

It is necessary to configure the distribution of the vendor data per company code and purchasing organization tothe different ECC regional systems. This will be configured using the ALE filters and a user exit associated to theIDoc generation. The aim of using a user exit is to stop the IDOC at source – if the vendor is not extended to apurchase org or company code:

The vendor and address data will be distributed to the regional systems where the company code and purchasingorganization belong to – as per requirement (1) and (7)

24 Customer Field update Restriction

(Requirement (4) – already implemented)

The following field must not overwrite for Account Groups () = ZOD(Owner Driver) or VCOM (Vending Commission) .This check is currently enforced for all vendors that do not belong to vendor account group “IC*”

LFA1 Customer KUNNR 10 CHAR

25 Customised Fields – BBBEE

(Requirement (3.1) – already implemented)

The following fields need to be sent as part of the vendor Creation and Update.

SAP Table name SAP Field name (functional)

SAP Field name (technical)

SAPField

length

SAP field type Mandatory

Target Field Name

TargetField

length

TargetField type

Mapping details

/BSA/TA_VNDPOIN1 Date from BEGDT 8 CHAR BEGDT 8 CHAR Direct Mapping/BSA/TA_VNDPOIN1 Reference vendor name NAME 35 CHAR NAME 35 CHAR Direct Mapping/BSA/TA_VNDPOIN1 DTI Class DTICLS 10 CHAR DTICLS 10 CHAR Direct Mapping/BSA/TA_VNDPOIN1 Recipient ED REC_ED 1 CHAR REC_ED 1 CHAR Direct Mapping/BSA/TA_VN

Enterprise Development Candidate

EDC 3 CHAR EDC 3 CHAR Direct Mapping


DPOIN1/BSA/TA_VNDPOIN1 Value Add VAL_ADD 1 CHAR

VAL_ADD 1 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 >= 50.1% black owned

BLACK_OWN 1 CHAR

BLACK_OWN 1 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 >= 30% Black women owned

BLACK_WOM 1 CHAR

BLACK_WOM 1 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 B2B BEE Level

/BSA/LEVEL 2 CHAR

/BSA/LEVEL 2 CHAR Direct Mapping

/BSA/TA_VNDPOIN1

B2B BEE Total Weighting Percentage

TOT_WEIGHTING 5 CHAR

TOT_WEIGHTING 5 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 VAT Registration Number STCEG 20 CHAR STCEG 20 CHAR Direct Mapping/BSA/TA_VNDPOIN1 New VAT registration number

/BSA/STCEG 20 CHAR

/BSA/STCEG 20 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Search Term 2 COMP_NO 20 CHAR

COMP_NO 20 CHAR Direct Mapping

/BSA/TA_VNDPOIN1

New company registration number

/BSA/COMP_NO 20 CHAR

/BSA/COMP_NO 20 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Comment

ZCOMMENT 250 CHAR

ZCOMMENT 250 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Rating Agency's Name

RATING_AGENCY 50 CHAR

RATING_AGENCY 50 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Score Card Link

SCORE_CARD_LINK 128 CHAR

SCORE_CARD_LINK 128 CHAR Direct Mapping

/BSA/TA_VNDPOIN1 Lock and unlock status STATUS 5 CHAR STATUS 5 CHAR Direct Mapping/BGT/VEND_EMAIL Plant WERKS_D 4 CHAR


/BGT/VEND_EMAIL



AD_SMTPADR 241 CHAR



26 Customised Fields – Vendor contacts

(Requirement (3.2) – already implemented)

The following fields need to be sent as part of the vendor Creation and Update.

SAP Table name SAP Field name (functional)

SAP Field name (technical)

SAPField

length

SAP field type Mandatory

Target Field Name

TargetField

length

TargetField type

Mapping details


/BGT/VEND_EMAIL Plant WERKS_D 4 CHAR


/BGT/VEND_EMAIL



AD_SMTPADR 241 CHAR



27 Sending of the Vendor IBAN and Address

5.1.5.1 Sending of the Vendor IBAN

The following ALE Config for the BAPI – IBAN_SAVERELICA, IBAN_CHANGE and IBAN_CREATEneeds to be implemented in order to send the IBAN number together with the vendor ALE:

Standard IBAN ALE config and an entry in the following table: TBDIBAN:

The table TBDIBAN entry contains the consolidation system for IBAN numbers.Note: The IBAN data is required in HR – HCM and Regional ECC for EU/LA and SA

5.1.5.2 Sending of the Vendor Address



ADRMAS (Address): apply vendor filter criteria in source. Once receiver is known, take object value from database, and then retrieve filter criteria for CREMAS for same sender / receiver (standard function), and compare database values against filter values (LFB1 and LFM1)

28 Sending of all POrgs for KRED Vendors


On the Outbound Message for Create or Change, send vendor records that are not markedfor deletion/blocked

29 Exclusion of Vendors that are blocked or Marked for Deletion

If value for Region = R in /BGT/MM_SYSLANDS: 1. Field SPERM in LFM1. This is the blocked indicator for a POrg. If any value is present

in this field then we want to exclude this POrg.2. Field LOEVM in LFM1. This is the deleted indicator for a POrg. If any value is present

in this field then we want to exclude this POrg.3. Field SPERR in LFA1. This is an “All company codes” block indicator. If any value is

present in this field then we want to exclude ALL POrgs.4. Field SPERQ in LFA1. This is a “Not to be used” block indicator. If any value is

present in this field then we want to exclude ALL POrgs.5. Field NODEL in LFA1. This is a deletion block indicator. If any value is present in this

field then we want to exclude ALL POrgs.

30 PARTNER PROFILE

It is required to create some custom fields in the vendor master, at basic level and at purchasing organizationlevel. These fields should be added to the CREMAS IDoc as an extension.

Parameter to configure ValuePartner type LSPartner Number Logical system assigned to global MDMMessage Type CREMAS

ADRMASInbound / Outbound OutboundReceiver Port Outbound port defined for ECC MDMPack Size 1Queue processingOutput Mode CollectBasic Type CREMAS05

ADRMAS03IBAN_SAVEREPLICA;IBAN_CHANGEIBAN_CREATE

ExtensionViewPost Processing: Type S / USPost Processing: Agent Position or user identified for executing

post processing for Vendor MasterPost Processing: Language EN


31 Change Pointers.

In order to get the IDocs from the source system it is required to configure change pointers for the messageCREMAS and ADRMAS.

Once that IMG point is accessed, a list with the different types of messages existing in the system is displayed. Itwill be required to search for the CREMAS and ADRMAS message types and mark the active flag. Then, at anytime a vendor is created or changed the system will be ready to send an IDoc.

To allow the system sending those IDocs any time a vendor is created or changed, it is required to schedule abackground job that triggers the transaction BD21 with entry parameter CREMAS and another for ADRMAS.This background job will execute the transaction that created the IDocs for the changes done in the vendormaster.


.

32 Job scheduling.

Job Name Program Variant Related system code

Business / application area code:

Job Frequency

SGECCMMH_CREMAS_DISTRIBUTION RBDMIDOC CREMAS ECC MM 5RBDMIDOC ADRMASRBDMIDOC CLFMASRSEOUT00 CREMASRSEOUT00 ADRMASRSEOUT00 CLFMAS

SGECCMMH_CREMAS_POSTING RBDAPP01 CREMAS ECC MM 5RBDAPP01 ADRMASRBDAPP01 CLFMASRBDAPP01 IBAN_CHANGERBDAPP01 IBAN_SAVEREPLICARBDAPP01 IBAN_CREATERBDMANIN CREMASRBDMANIN ADRMASRBDMANIN CLFMASRBDMANIN IBAN_CHANGERBDMANIN IBAN_SAVEREPLICARBDMANIN IBAN_CREATE

33 CONTINGENCY

The IDoc list can be identified in WE02 transaction. There can be multiple ways to handle contingencies – In case of no extraction (or extraction failures), cost center master data can be re-extracted through a

manual transaction BD14 When the IDoc is not received in the target system, a new run of the program must be executed If the IDoc is not processed in the target system – whenever feasible, manual handling is required. For

manual processing and error identification, transaction BD87 can be used. Alternatively, the program RSEOUT00 can be used to re-send all IDoc records marked in ‘Ready for

processing’ status

34 PROCESS AND OPERATIONAL CONSIDERATIONS


Maintenance Requirements

Archiving/Deletion Considerations

Security Requirements

Usability / Accessibility

Availability

Legal Requirements / SOX

Reporting/Monitoring Requirements IDocs monitoring required

Other

35 ERROR HANDLING

Error handling will be managed through a user allocated for post processing. This user should get in touch withthe business in order to communicate those errors. Errors that should be escalated to business are all related tomissing configuration, misalignment between configuration in the central and regional system and similar things.No technical error should be escalated to business users.

Error type Action AgentTechnical Identify technical error and search

for the solution.IDoc Administrator

Functional Communication to business agentand reprocess after issue is solved

Vendor Master data OperationalLead per Region ( current approachis a position in HR organizationstructure)

Potential Errors Possible Reasons Solution StrategyNot partner profile found out Distribution model

wrongly configuredReview Distribution model and amend it / Mail to technical team

Data does not reach target system RFC connection down Check connection andresend message

Error in inbound interface Configuration values notaligned

Escalate ( mail or anycommunication actiondefined by the integrationteam ) in order to identifywhy configuration is notaccurate and sameReprocess IDoc

Error in outbound interface ALE distribution notimplemented correctly

Verify SALE transaction tocheck distribution andresend IDocs.


36 TESTING REQUIREMENTS

Test Script Expected resultsDIST_1 Vendor in SAP ECC is distributed successfully into regional systems

DIST_2 Vendor address is changed in SAP ECC is distributed into regional systems

DIST_3 Vendor company code data is changed and is distributed to the right ECC regionalsystem and not transferred to the other two systems.

DIST_4 Vendors purchasing organization data is changed and distributed to the right ECCregional system and not transferred to the other two systems

DIST_5 Customer address details are changed and BD21 transaction understands thatthere is a change. Distribution model does not send ADRMAS as a filter is set up toavoid it.

DIST_5 Maintain BBBEE Data on a VendorAll the Vendor BBB-EE data needs to be distributed across together with the vendorrecord according to the distribution model i.e if the vendor is going to S.Africa, theBBB EE data must only be sent to South africaZFIBBBEEUP Upload BBBEE vendor score cardsZFIVENSPEQT1 Maintain Sector and TextZFIVENSPEQT2 Maintain Scorecard & ExemptionZFIVENSPEQT3 Maintain DTI WeightingZFIVENSPEQT4 BBB-EE ReportZFIVENSPEQT5 Maintain vendor equity points

DIST_6 Customer value from sending system, completed or not completed to be ignored onInbound processing of the ALE in the receiving system. Exception to the rule will beVendor Account Groups starting with an “IC” for example ICPT, IPTN, etc to processnormal and apply value to Regional ECC.

DIST_7 Extend a Vendor to an Additional POrg – Check if the ALE resend all other POrgswhere the vendor is already extended

DIST_8 Change Address detail on a Vendor– Check if the ALE resend all the POrgs withthe vendor record

DIST_9 Create a Vendor with an IBAN number and ALE the Vendor across – IBAN numbermust be sent with the vendor information

DIST_10 Change the Vendor’s IBAN and ALE it across - new IBAN number must be sent withthe vendor information

DIST_111. CREMAS (Vendors): stop basic views from distributing

without a company code or purch org data, enhancement in sender system

2. ADRMAS (Address): apply vendor filter criteria in source. Once receiver is known, take object value from database, and then retrieve filter criteria for CREMAS for same sender / receiver (standard function), and compare database values against filter values (LFB1 and LFM1)

37 DESIGN CONSTRAINTS


38 Open Issues

The following issues are currently being experienced in Production:- The restriction to the sending of customer field is not working in QA but is working in Production The sending of the BBBEE and Contact is not working in PROD GP7 500 though it was working post Go

live There is current logic that needs to be removed that restricts vendor sent according to account group.

There is no business requirement for this logic


39 APPENDIX

40 Purchase Organisations per Region

Please note that Europe and LATAM are in a single instance and Global goes to both S.Africa and LAT/EUinstance,

Source SAP System

Idoc Message Type

Target SAP System

Purchasing Org

Notes

GP7CLNT500 CREMAS BP1CLNT500 0PLC

GP7CLNT500 CREMAS BP1CLNT500 0R05



GP7CLNT500 CREMAS BP1CLNT500 1100









GP7CLNT500 CREMAS BP1CLNT500 1ACO

GP7CLNT500 CREMAS BP1CLNT500 1AES

GP7CLNT500 CREMAS BP1CLNT500 1AG

GP7CLNT500 CREMAS BP1CLNT500 1AN

GP7CLNT500 CREMAS BP1CLNT500 1AP

GP7CLNT500 CREMAS BP1CLNT500 1AR

GP7CLNT500 CREMAS BP1CLNT500 1AV









GP7CLNT500 CREMAS BP1CLNT500 1RNP

GP7CLNT500 CREMAS BP1CLNT500 1SA

GP7CLNT500 CREMAS BP1CLNT500 1SB

GP7CLNT500 CREMAS BP1CLNT500 1SCO

GP7CLNT500 CREMAS BP1CLNT500 1SD

GP7CLNT500 CREMAS BP1CLNT500 1SE


GP7CLNT500 CREMAS BP1CLNT500 1SH

GP7CLNT500 CREMAS BP1CLNT500 1SJ

GP7CLNT500 CREMAS BP1CLNT500 1SM

GP7CLNT500 CREMAS BP1CLNT500 G001



































GP7CLNT500 CREMAS BP1CLNT500 1AU















GP7CLNT500 CREMAS BP1CLNT500 1BA

GP7CLNT500 CREMAS BP1CLNT500 1BC














GP7CLNT500 CREMAS BP1CLNT500 1HF
















































GP7CLNT500 CREMAS EP7CLNT500 5CA1




GP7CLNT500 CREMAS EP7CLNT500 5R01







GP7CLNT500 CREMAS EP7CLNT500 G001






































GP7CLNT500 CREMAS BP1CLNT500 1ACO

GP7CLNT500 CREMAS BP1CLNT500 1AES

GP7CLNT500 CREMAS BP1CLNT500 1AG

GP7CLNT500 CREMAS BP1CLNT500 1AN

GP7CLNT500 CREMAS BP1CLNT500 1AP

GP7CLNT500 CREMAS BP1CLNT500 1AR

GP7CLNT500 CREMAS BP1CLNT500 1AU

GP7CLNT500 CREMAS BP1CLNT500 1AV

GP7CLNT500 CREMAS BP1CLNT500 1BA

GP7CLNT500 CREMAS BP1CLNT500 1BC

GP7CLNT500 CREMAS BP1CLNT500 1HF











GP7CLNT500 CREMAS BP1CLNT500 1SA

GP7CLNT500 CREMAS BP1CLNT500 1SB

GP7CLNT500 CREMAS BP1CLNT500 1SCO

GP7CLNT500 CREMAS BP1CLNT500 1SD

GP7CLNT500 CREMAS BP1CLNT500 1SE

GP7CLNT500 CREMAS BP1CLNT500 1SH

GP7CLNT500 CREMAS BP1CLNT500 1SJ

GP7CLNT500 CREMAS BP1CLNT500 1SM





















































Added for SAB distributers list see CR48969(18/06/2012)











Company codes per region: Source SAP System

Idoc Message Type

Target SAP System

Company Code

GP7CLNT500 CREMAS BP1CLNT500 0002Confidential and Proprietary of 44









GP7CLNT500 CREMAS BP1CLNT500 0061 New





































































Added since Anna could send vendors to BP1


GP7CLNT500 CREMAS EP7CLNT500 5300

GP7CLNT500 CREMAS EP7CLNT500 5302

GP7CLNT500 CREMAS EP7CLNT500 8201PL company code



GP7CLNT500 CREMAS EP7CLNT500 8205 PL company


code



This entries should be include in BAU August 2012






This entries should be included in BAU August 2012















GP7CLNT500 CREMAS BP1CLNT500 0430 This entries


should be included in BAU August 2012


Added for SAB distributers list see CR48969 (18/06/2012)












41 Check criteria

Report Specific Criteria Yes/No CommentsDocument has been flagged with SOX keywords.Each section has been filled out with meaningful andappropriate information, with n/a if not applicableProcess flow diagram is provided and effectivelycommunicates the end-to-end process from a businessperspective. If it is a manual process, clearly illustratethis with a “stick figure”.The translation requirements have been provided.Test requirements have been provided in the form ofspecific test conditions/results.Performance considerations/constraints aredocumented as appropriate.Identify source and target systems. Specify initiation method for event driven (i.e.,synchronous and asynchronous) interfacesSpecify System information , logical & physical path Give accurate data mapping from source and targetsystem (e.g., field lengths, table name, fields,.)Specify volume and frequency
