on 12-08-2014 12:28 PM
Hi,
Why is loading rules of origin from an XML file a transportable change while loading a SPL or HTS XML file not?
To load the rules of origin we are using transaction /SAPSLL/PREF_RLS_UPL.
Thank you, Jeff
Hi Jeff,
I think you need to consider the impact of the client settings on the upload program:
1. Changes without automatic recording
Upload WITHOUT transport request and there are no data scope options available in the program.
2. Automatic recording of changes
Upload WITH transport request and there are no data scope options available in the program.
3. No changes are allowed
With this setting there is no transport request but you have some data scope options available in the program.
4. No transports are allowed
Similar to 1.
Please check transaction SCC4 for the client you are working in.
Then we also have to consider the distinction between the customizing data and master data that the file might contain.
In some landscapes all the customizing data is uploaded to a central customizing client and then transported downstream to the other clients. Then only the actual master data is uploaded to the individual clients.
Best Regards,
Eoin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
16 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.