Saving customer fields to SAP table (EXIT_SAPMM06E_012)

Question

Hi All,
I would like to ask you guys a bit of a help with a user exit that I am working on as of the moment.
I am coding a user exit for a service purchase order (ekpo-knttp = 'K' and ekpo-pstyp = 'D') this is a service purchase order of cost centre category.
Since SAP does not allow the goods recipient (ekkn-wempf) to be modified for reasons specified in SAP Note 118008. I have used user exit MM06E005 FMs EXIT_SAPMM06E_017, EXIT_SAPMM06E_016 to the data in PBO and PAI for the transaction.
Now I tried using the two FMs EXIT_SAPMM06E_018 and EXIT_SAPMM06E_012 to pass this value to the table but it does not seem to get saved in table EKKN.
Using FM EXIT_SAPMM06E_018  the I have maintained the structure CI_EKPODB to include WEMPF and after debugging passing that user exit area the wempf is being tranfered to global data but this does not get saved in EKKN table (EKKN-WEMPF).
Although this is outside of the standard best practice of SAP since the account assingment belongs to the limits or the service line for service order but maintaining this recipient field for the PO item does not impact our system processes as the business acknolwedges goods recipient for service PO.
BADI ME_PROCESS_PO_CUST has also been implemented under method PROCESS_ACCOUNT invoking the interface IF_PURCHASE_ORDER_ACCOUNT_MM but unsucessful in the operation.
If anyone of you guys has encoutered same scenario or implementation requirement please do give information on this or work-arounds are well appreciated as well.
Cheers,
Erwin

Answer 1

Hi,
We have worked on a similar requirement ,just check if its useful to you.
Requirement:
                     You have to add the custom field in SAP standard table EKKO. Then we have to place the field in ME21N screen. When user enters any input into the field it should get updated in the database.
Note:
                     EKKO table is meant for Purchasing document header, you should add the field in the header level for ME21n screen. There you are provided with customer sub screens where you can add the field in the screen.
Procedure:
1You have to create a field in the Custom Include of standard table, after creating activate it.
2.Double click on the include then you can add your custom field here.
Find out the Required Enhancements:
1.Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton u2018Information systemu2019.
2.Then mention the particular package name of the transaction you need to      enhance. Then you will be shown the list of Enhancement components for that particular package.
3.Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
MM06E005 is the Enhancement component we are using here.
Development
Creating a Project to include the enhancement:
1.Go to transaction CMOD and create a project.
2.Enter a description for the project.
3.Then, click on the pushbutton u2018Enhancement Assignmentsu2019 in the Application Toolbar.
4.Click on the components in Application Toolbar.
5.Here you will be shown the function module exits, screen exits and Include tables.
6.Click on the custom screen SAPLXMO6 u2013 0101 in which it suits the requirement of adding the custom field to the layout
7.Click on layout and go to get from dictionary and select the field you need to add and click ok.
8.Place the field in the layout and activate it.
9.After that you come back and check the respective function module in which you need to implement the code. So, we need to import the data from sub screen for purchasing document header. Therefore we have chosen  the  EXIT_SAPMM06E_008.
10. Write code in the Function Exits to synchronize the programs:
                   Now, code has to be written in the function modules EXIT_SAPMM06E_008 so that data flows to and fro between the main SAP program and custom sub screen program. Double clicking on the exit we get the following screen.
11. Double click on the include and write the required code inside it. Then activate it.
TABLES:EKKOIF NOT EKKO_ZADD IS INITIAL.
MOVE EKKO-ZADD  to e_ci_ekko-zadd.
move corresponding  e_ci_ekko to ekko.
modiky ekko  from ekko.
12. Now come back and activate the entire project.
13. Now go to ME21n transaction and create a purchase order by giving all the mandatory fields including custom field we have created. Here Test is the custom field we have created. After entering the data then press SAVE button, your data will be populated to the respective table.
14. Go to SE11 or SE16n, check whether the field got updated in the database or  not in EKKO table.
Thanks,Surya Pydikondala.
      Finally it gets updated in the database.