Skip to Content
0
May 29, 2008 at 02:38 PM

changing Delta to Full Load 0co_om_opa_6 * points

76 Views

hello guys, i have a scenerio where i am making the delta load in to a full load.

i have created a process that loads 08 data only as a full load every day. the infopackage is brand new and doesnt exists in production system.

when i test my chain in development, it works fine, when i transport it to testing, it transports fine and runs correctly, but when i transport it to production, it has error son transport, and when you click on the infopackage from RSA1, the infopackage cannot even find it self being part of the process chain.

the error message is as follows..

1)Start of the after-import method RS_RSPC_AFTER_IMPORT for object type(s) RSPC (Activation Mode)

2) Processes with Error

Message no. RSPC022

Diagnosis

Error occurred when checking the process chain.

When errors occur, the system does not activate the chain.

Procedure

Call the relevant messages for the processes that are marked in yellow and red using the context menu.

3) Errors occurred during post-handling RS_AFTER_IMPORT for ISIP L

Message no. PU133

Diagnosis

During the upgrade, import post-processing RS_AFTER_IMPORT was performed for object ISIP L. Errors were reported.

4) BW-WHM (Warehouse Management)

Message no. PU137

Diagnosis

During the upgrade or import of a transport request, errors occurred in the component

BW-WHM (Warehouse Management).

i have checked the production system , a delta init is already defined there. so my question is do i have define my infopackage as a "delta without data tarnsfer" tranport it then redfine it as a full load and

transport it again and it should work.

any suggestions

i am trying to understand why am i getting this error and what is the best practice to transport an infopackage as a full load on a delta extractor.