cancel
Showing results for 
Search instead for 
Did you mean: 

Unloading Point field not included when copying a PO in portal

Former Member
0 Kudos

Hi Experts,

We have enabled the unloading point field in the item overview table of a PO in web dynpro /SAPSRM/WDC_UI_PO_DOTC_IT. When we try to copy an existing PO, the newly copied PO will not copy the unloading point that was available in the original PO. It is not passed to the DOC_CHANGE_BADI as well under the field BE_UNLOAD point. Is there a way this can be achieved? or any additional config that we are missing to enable this by default. Please help.

Thanks!

Pavithra Kumar

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi All,

The issue has been identified.

The field BE_UNLOAD_PT is considered as a back-end field by SAP. So even if available in the original PO, when we copy the PO all backend reference is being cleared and thus not carried forward to the new copy PO. Hence when you want to enable the unloading point, it will not be available only for copy PO/ shopping cart scenario.

Thanks for all the inputs.

Regards,

Pavithra

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Pavithra,

I assume you are trying to populate the "Storage Location" value in the field "BE_UNLOAD".

If yes, I would suggest you to verify the values maintained in the field "Storage Locations" of the "Extended Attributes" for the user ID in the PPOMA_BBP.

We have worked on a similar requirement to populate the SLOC values in the field "Unloading Point" by reading the SLOC's maintained under the extended attributes for a user ID using standard FMs.

Br,

Raghu

Former Member
0 Kudos

Hi Raghu,

Thanks for your inputs!

We have a separate look up table in ECC which will be used to populate the values in BE_UNLOAD. When we try to change or create the PO in portal we don't see any issue in the value retaining in the field. Issue appears only when we copy an existing PO, the value that was there in the original PO was not retained in the copied PO.

Please let me know if my explanation detail the issue.

Thanks!

Former Member
0 Kudos

Hi Pavithra,

In this case, I would use read the data in the field BE_UNLOAD from the table CRMD_ORDERADM_I (Item data) by passing the:

- PO GUID (which is being used as a reference)

- The corresponding Item number

Use the BBP_DOC_CHANGE_BADI to populate values in the field BE_UNLOAD in the new PO.

See if this works for you..

Br,

Raghu.

Former Member
0 Kudos

Hi Raghu,

The problem here is the value does not populate in the field BE_UNLOAD when the BADI is called which should be done as its a standard field. Moreover while I create a PO from copy, it will have a temp GUID and so no data will be available in any table for force read in the change_badi. The basic problem is the original PO value for unloading point is not transferred to the new one. So we are wondering if this has something to do in the standard. Please let me know if this makes some thought for you. 

Thank You

Former Member
0 Kudos

Hi Pavithra,

I am slightly confused when you mention about the temp GUID.

I agree that would happen when you create a new PO however, the reference PO that you would use would have a GUID which you can pass to the CRMD item table to fetch the values already present in the BE_UNLOAD.

Can you confirm if you are able to fetch the values maintained in the existing PO's.

Br,

Raghu