1.

The whole migration of the data of the divested company code was done by a third party named
SNP
2. Always a rule set is given to SNP based on which they migrate the data from one server to the
other.
Rule set comprises of which
 sales document needs to be migrated based on their status
 the new org elements like profit center, plants, needs to be mapped against the old org
elements.
3. The migration was done in multiple phases to reduce the numbers of errors at source and
destinations
4. Proper testing was done at each mock, to ensure all the new org elements are mapped properly
against their respective old org elements.
5. Source closing after go-live
6. Forms separation by BOPF table

(The Business Object Processing Framework is an ABAP OO-based framework that provides a set of
generic services and functionalities to speed up, standardize, and modularize your development.
BOPF controls the application business logic as well as the data retrieval of the buffer and persistency
layer. The main design principles are a clear separation of the business logic and the buffering of data as
well as a clear structuring of the business logic into small parts with a clear separation of changing and
checking business logic.)
The enhancement has been done, created custom table to configure PG specific forms/programs along
with the details to redirect the PG output using same existing output type.

 New programs and forms (Script and Smart forms) can be called as per the entries configured in
custom table with the same output type
 Entries can maintain directly in production (no transport movement required)
 Old forms will continue to work as per current NACE configuration with the same output type
 Custom table structure as below
o Client - SAP client (400, 500.. etc.)
o System ID (SID)/SAP system - RD4/RT1/RP1
o Sales Org. - PG Sales Org.
o Application - V1/V2/V3/V4/V6/V7
o Output type - ZAE1, ZNZ1.. etc.
o Medium - 1 (Print output), 2 (Fax), etc.
o Form type - SS (Script)/ SM (Smartform)
o Program name - Driver program name
o Form name - Script/Smartform name
o Activation Date - From which date system should print new form (Date will be compared
with the document creation date if maintained, system by default print new forms if
date is blank)
o De-activation - De-activates the entry (logical deletion)
 Entries can be configured in custom table as below
o Run tcode ZSDTABMNT
o Enter Business object name ZSD_PGFORMS_CONFIG
7. All client setups were done- Pre-SNP activities (TVARVC, SETs & BRF+)
8. Plant Locking
9. Org units locking
10. Invoice Number Ranges
11. Employee Replication
12. Batch Jobs
13. Duplication setup of the interface are done for both clients
14.