or (Customer doesn't have central deletion indicator AND Customer has active sales view data within the sales organizations in scope) and there is usage within 4 years.

Select KUNNR from KNA1 where KNA1-LOEVM="" and KNVV-KUNNR = KNA1-KUNNR AND KNVV-VKORG in (Sales Org in scope) and KNVV-LOEVM = "" and usage within 4 years. 

1. Accounting document (Select MAX(BSAD/BSID-CPUDT) where BSAD/BSID-KUNNR =KNA1-KUNNR and BSAD/BSID-BUKRS = (Company code in scope) )
2. Sales Document (Select MAX(VBAK-ERDAT) WHERE VBAK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
3. Delivery Document (Select MAX(LIKP-ERDAT) WHERE LIKP-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
4. Billing   (Select MAX(VBRK-ERDAT) WHERE VBRK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)

or (Customer doesn't have central deletion indicator and customer has active company code view within the company codes in scope) and there is usage within 4 years

Select KUNNR from KNA1 where KNA1-LOEVM="" and KNB1-KUNNR = KNA1-KUNNR AND KNB1-BUKRS in (Company code in scope) and KNB1-LOVEM = "" and usage with 4 years

1. Accounting document (Select MAX(BSAD/BSID-CPUDT) where BSAD/BSID-KUNNR =KNA1-KUNNR and BSAD/BSID-BUKRS = (Company code in scope) )
2. Sales Document (Select MAX(VBAK-ERDAT) WHERE VBAK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
3. Delivery Document (Select MAX(LIKP-ERDAT) WHERE LIKP-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
4. Billing   (Select MAX(VBRK-ERDAT) WHERE VBRK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)

Select KNVP-KUNNR INNER

JOIN KNA1 as a WHERE KNVP-KUNNR = a.kunnr and a.loevm = X and KNVP-VKORG in 'Sales Org in scope'

inner join kna1 as b where knvp-kunn2 = b.kunnr and b.loevm  = '' and kunn2 in rule 2

Two reports will be provided.

iCare - If (there is value in field 'PRS Code (Account)' or 'RCS code (Account)') and 'Last Activity' is within 48 months and Type <> "Inactive Customer". then the account is in scope. 'PRS Code (Account)' is mapped to PF2 customer number, 'RCS code (Account)' is mapped to WP2 customer number.

Core CRM - If (there is value in field 'PRS ID / RCS ID') and 'Last Activity' is within 48 months and 'Account Organization' = 'SCO' and 'Status'<>"Rejected", then the account is in scope. 'PRS ID / RCS ID' need to split using "/" to get the PRS/RCS code and 'GBU'  in (Novecare, Technology Solutions). 

• This will be parked for now

or there is relevant Pricing Condition records maintained for the customer 4 years ago.

a. The relevant condition table will be provided, which includes the customer field

b. The price valid-from date is >= current date - 4 years 

c. Based on the selection criteria mentioned in a&b to select the condition header index table (KONH), then use it to match the customer number. If there is match, then the customer is taken into consideration.

Select  KNA1-KUNNR from KONH where KONH-KOTABNR IN (List to be provided) and KONH-DATAB >= current date - 4 years  and  KONH-VAKEY CS KNA1-KUNNR

One time customer (Account group is Z004)

Mapping Table Name

Description

Legacy Customer-BP Master Mapping

Legacy to S4 Business Partner customer mapping

Business Partner deDupe mapping (Global Data)

dedupe Golden-child (Global) mapping

Company Code Mapping

Legacy to S4 Company Code Mapping

Payment Terms Mapping

Legacy to S4 Payment Terms Mapping

Payment Method Mapping

Payment Method Mapping

Tax Category Mapping

Legacy to S4 Tax Category Mapping

Reconciliation Account Mapping

Legacy to S4 Reconciliation Account Mapping

Sort Key Mapping

Legacy to S4 Sort Key Mapping

Planning Group Mapping

Legacy to S4 Planning Group Mapping

deDupe customer Company Code Nominations Mapping

Golden-Child Company Code data Mapping

1

Load Sample Business Partners

Data

2

Validate sample Business Partners

Data

3

Load remaining Business Partners

Data

4

Validate data loaded for Business Partners

Data

5

Load Sample BP Type – Customer Contact Persons

Data

6

Validate sample BP Type – Customer Contact Persons

Data

7

Load remaining BP Type – Customer Contact Persons

Data

8

Validate data loaded for BP Type – Customer Contact Persons

Data

9

Load Sample BP Type – Vendor Contact Persons

Data

10

Validate sample BP Type – Vendor Contact Persons

Data

11

Load remaining BP Type – Vendor Contact Persons

Data

12

Validate data loaded for BP Type – Vendor Contact Persons

Data

13

Load Sample BP Type - Bank Contacts (First Name, Last Name)

Data

14

Validate sample BP Type - Bank Contacts (First Name, Last Name)

Data

15

Load remaining BP Type - Bank Contacts (First Name, Last Name)

Data

16

Validate data loaded for BP Type - Bank Contacts (First Name, Last Name)

Data

17

Load Sample BP Type – BP General, FI Customer, FI Vendor

Data

18

Validate sample BP Type – BP General, FI Customer, FI Vendor

Data

19

Load remaining BP Type – BP General, FI Customer, FI Vendor

Data

20

Validate data loaded for BP Type – BP General, FI Customer, FI Vendor

Data

21

Load Sample Vendors Default Partner

Data

22

Validate sample Vendors Default Partner

Data

23

Load remaining Vendors Default Partner

Data

24

Validate data loaded for Vendors Default Partner

Data

25

Load Sample BP - General for remaining customer roles

Data

26

Validate sample BP - General for remaining customer roles

Data

27

Load remaining BP - General for remaining customer roles

Data

28

Validate data loaded for BP - General for remaining customer roles

Data

29

Load Sample BP – Customers with Default Partner

Data

30

Validate sample BP – Customers with Default Partner

Data

31

Load remaining BP – Customers with Default Partner

Data

32

Validate data loaded BP – Customers with Default Partner

Data

33

Load Sample BP - Bank Role

Data

34

Validate sample BP - Bank Role

Data

35

Load remaining BP - Bank Role

Data

36

Validate data loaded BP - Bank Role

Data

37

Load Sample BP Relationship Contact Person to Organisation (Will create KNVK records)

Data

38

Validate sample BP Relationship Contact Person to Organisation (Will create KNVK records)

Data

39

Load remaining BP Relationship Contact Person to Organisation (Will create KNVK records)

Data

40

Validate data loaded for BP Relationship Contact Person to Organisation (Will create KNVK records)

Data

41

Load Sample BP - Carrier

Data

42

Validate sample BP - Carrier

Data

43

Load remaining BP - Carrier

Data

44

Validate data loaded BP - Carrier

Data

45

Load Sample BP - Credit Management

Data

46

Validate sample BP - Credit Management

Data

47

Load remaining BP - Credit Management

Data

48

Validate data loaded BP - Credit Management

Data

49

Load Sample BP Collections Management

Data

50

Validate sample BP Collections Management

Data

51

Load remaining BP Collections Management

Data

52

Validate data loaded BP Collections Management

Data