Transferring Plant Specific data from ECC

[former_member623543]

Hi all,

Our company has previously used the /SAPSLL/PRGEN table to store material data from ECC such as Cross Plant Material status to display in GTS.  We have been asked to also include the Country of Origin information from the Foreign Trade: Export tab in ECC, but our ABAP developers are getting errors about trying to move plant specific data.  I understand that the CoO is transferred to GTS transactionally when performing its checks, but we have had requests to simply copy the data over for viewing in the GTS client.

Has anyone had any luck trying to fill these data tables with plant specific data of any kind?  Is there any documentation for possible configuration set up required?

My ABAP expert mentioned that her errors were pointing her toward the MODWG and MODWRK tables, but so far, our GTS implementation has not had any use for these tables.

[Former Member]

Hi Ben,

Did you try using the product attributes options provided by SAP?

I had tried this once to transfer the product hierarchy and update that in GTS. When you define a product attribute in GTS, you can make use of EXIT_SAPLSLL_LEG_PRR3_004 and fill the CoO to that attribute.

You can use the same and try to push the CoO to GTS for a product.

Thanks

Dhilipan

[former_member215181]

Hi Ben,

Filling data tables is not generally a matter of luck .  Unfortunately in this instance, it sounds like a case of IT slavishly following a business request without either side understanding it.

GTS is capable of holding CofO data in the Preference Management area, and table /SAPSLL/PRPREFR3 (field PURLA) would be used for that, but the country code would be determined, not copied from the feeder system directly.

Assuming that implementing Preference Management isn't currently in scope, the business should be challenged as to their reason(s) for wanting to hold CofO as master data in GTS.  Just "wanting to display it" doesn't count as an answer, I'm afraid.  "Wanting to display it so that the following necessary process action(s) can be taken:..." might start to provide some justification.

As you say, CofO is already transferred as part of the transactional data, and for most purposes that should be sufficient.  If, for some unusual reason, you do end up having to transfer it as master data, then you should probably set up some basic Preference data to provide a Model key for the PRPREFR3 data, then ask your "ABAP expert" to write her own extractor and API to transfer it - there's nothing standard as far as I know.

Hope that helps,

Regards,

Dave