Ship to Re-Partnering

Question

Hi Experts,
I am sending a part of  FS which I won't be able to understand.Please tell me how to do the coding.
5. DESIGN / BUSINESS BACKGROUND
MDM goes through a tedious data clean-up process when moving one ship-to partner from one sold-to partner to a new sold-to partner.
They are required to delete the ship-to partner from current sold-to location in all sales organizations.  Then partner the sold-to information for each sales organization.
If the ship-to location has a business location ID.  Expire the current role and change the operator to the new Sold-to. 
Designing a program to accomplish the above steps to will improve data integrity and reduce the number of accounts to manage. 
DESIGN REQUIREMENTS
SCOPE OF CHANGES (Identify the work required, configuration, report layouts, selections, forms etc.  Provide table/field names, transactions etc.)
3.     Ship-to
4.     Ship-to Name
5.     Sales Org u2018CA01u2019 Available u2013 type character length 1.
6.     Sales Org u2018CA02u2019 Available u2013 type character length 1.
7.     Sales Org u2018CA03u2019 Available u2013 type character length 1.
8.     Operator Code Valid u2013 type character length 1 u2013 from valid ZOPE role in OIFBBP1 use todayu2019s date and time for FTMSTM and TTMSTM.
9.     Message u2013 for pre-post transfer message processing.
10.     Original Sold-to Number
11.     Original Sold-to Name
12.     New Sold-to Number
13.     New Sold-to Name
Develop a program ZSD_CST001 u2013 Customer Re-Partnering (rename transaction ZSD2) that can re-partner only ship-to locations from one ship-to partner from one sold-to partner to a new sold-to partner.  Produce an exception log for any bill-to, payer, customer contact information that has moved but could possibly be incorrect.  Create a new role in the Business Location ID.
Using an ALV only allow user to move records that can be transferred:
u2022     Only allow ship-to transfer for non-marked for deletion records. 
u2022     Only allow transfer of ship-to records that are currently partnered to sold-to. 
u2022     Do not allow transfer of ship-to records that have different sold-to/bill-to/payer accounts.  These will need to be move manually.  
u2022     Contact persons, load confirmation contacts and any other partner function will be allowed to move.
u2022     Only allow change if the valid Operator number is the same customer number as the sold-to or the re-partnered sold-to.
Create a button called u2018Transferu2019 to move the ship-to locations from one sold-to to the next.  Allow a mass selection of all lines and then transfer all.  The log should update the current report describing the success to the user.  User should be able to filter on error messages or completed message.
Future functionality can be developed in later requests to allow transfer of ship-to records that have different partner functions attached.  However this will be out of scope in the original rollout.
Transactional Steps
1.     The first step is to remove the ship-to from the SH partnering of the sold-to number.  Using VD02:
a.     Enter in Sales Area Data.
b.     Continue.
c.     Click on Sales Area Data screen
d.     Click on Partner Functions tab. 
e.     Enter in SH partner function and ship-to number. Click Enter.
f.     Select first line and click Delete row button.
g.     Save.
2.     Add the ship-to number as an SH partner to the new sold-to number.  This is done using VD02 on the Sales Area Data screen  Partner Function tab.  Same as above transaction.
3.     If the ship-to location has a business location ID.  Expire the current role and change the operator (ZOPE) to the new Sold-to.  This is completed with transaction O402. 
a.     Select the line with the ZOPE and the same customer number.
b.     Click on the change line and add in the End Date as the last day of the previous month (there is a function call for this, check ZPACRS.
c.     Click back. 
d.     Click the create button, enter u2018ZOPEu2019 role, start date is first day of current month, 00:00 as time and end date 2009/12/31. 
e.     Click Enter. 
f.     Enter in new Sold-to Party number. 
g.     Click back.
h.     Save.
Selection Screen:
Current Partnering Data:                Type
Sold-to Partner                      Parameter
Ship-to                      Selection Option
Transfer Ship-to Documents to:                
Sold-to Partner                      Parameter
ALV Layout Column Set
3.     Ship-to
4.     Ship-to Name
5.     Sales Org u2018CA01u2019 Available u2013 type character length 1.
6.     Sales Org u2018CA02u2019 Available u2013 type character length 1.
7.     Sales Org u2018CA03u2019 Available u2013 type character length 1.
8.     Operator Code Valid u2013 type character length 1 u2013 from valid ZOPE role in OIFBBP1 use todayu2019s date and time for FTMSTM and TTMSTM.
9.     Message u2013 for pre-post transfer message processing.
10.     Original Sold-to Number
11.     Original Sold-to Name
12.     New Sold-to Number
13.     New Sold-to Name
Program Syntax
The changes can be completed using BDC or BAPI preferably a BAPI for increased speed.
This transaction will eventually utilize Workflow.  Develop de-partnering, re-partnering, and adding new partner transfer within ZCL_KNVV classes if this transaction gets moved to a Web Dynpro application.  Pass in a similar class with three partner numbers and return the success for each transaction.  This can be grouped into one class to handle the entire transfer.  This functionality will be used in a future project for deactivating accounts.

Answer 1

If you don't understand your requirements, then you should talk to the person who gave then to you, not the forum - locked.