Datasource Time Stamp Error

Error Description: Datasource Time Stamp Error
*Solution: Replicate and Activate Datasource & Transfer Rules Directly in WBP *

+Instructions for BW 3.x datasource replication

Go to RSA1 -> Modeling -> InfoProvider

Right click on the datasource and select Replicate Metadata.

Go to transaction code SE38 and execute the program RS_TRANSTRU_ACTIVATE_ALL to activate the transfer structure.

Input the technical names of the Source System and InfoSource that are related to the replicated datasource. Click execute to activate the infosource.

Proceed to repeat the loading in the process chain.

+Instructions for BI7 datasource replication

Go to RSA1 -> Modeling -> InfoProvider

Right click on the DataSource and select Replicate Metadata.

Go to transaction code SE38 and execute the program RSDS_DATASOURCE_ACTIVATE_ALL to activate the Datasource structure.

Input the technical names of the Source System and DataSource that was being replicated. Click execute to activate the datasource structure.

Go to transaction code SE38 and execute the program RSDG_TRFN_ACTIVATE to activate the Transformation related to the replicated DataSource.

Input the technical name (ID) of the Transformation that is related to the replicated datasource. Enter ACT in the OBJSTAT field. Click execute to activate the transformation structure.

Proceed to repeat the loading in the process chain.

===========================================================================================================================

SYSTEM NO ROLL in DTP

Error Description: SYSTEM NO ROLL in DTP
Solution: Reduce the DTP package size
Instructions: Click on the button in the red box to view the short dump details.

• !Attachment Library^untitled.bmp|alt="SYSTEM NO ROLL Dump.bmp" ! *
  Or go to transaction code ST22 to view the short dump as shown below.

In the DTP’s Extraction Tab, reduce the value of the Package Size and then activate the DTP.Then execute the loading again from the Execute Tab. When prompted, choose Delete instead of Repair.

• *

After the manual loading have completed successfully, go back to the process chain and right click on the error process and choose "Repair".

===========================================================================================================================

Process Chain Processes 'Hanged' Issue

Error descripition: Processes of a process chain have completed successfully but does not trigger the subsequent process to run causing the whole chain to 'hanged'.Solution: Use the table RSPCPROCESSLOG and the function module RSPC_PROCESS_FINISH to manually trigger the subsequent processes.

Note: To use this to correct the loadings, please make sure that the “hanged” process involved is really successful before to carry out the following steps.

Step 1: Open the process chain and click on the logs button to view the logs.

!Attachment Library^hanged1.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 2: Double-click on the “hanged” process to view the details.

!Attachment Library^hanged2.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 3: Click on the “Chain” tab to view the technical details of this process log.

!Attachment Library^hanged3.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 4: Take note of the 3 fields that are being boxed-up in red below as you will need to use it in Step 6.

!Attachment Library^hanged4.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 5: Go to transaction SE16 and enter the table name RSPCPROCESSLOG and press enter button on the keyboard to continue.

!Attachment Library^hanged5.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 6: Copy the values of the boxed-up fields of Step 4 and paste them into the fields below. Then click execute.

!Attachment Library^hanged6.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 7: Click on the button below to view the record.

!Attachment Library^hanged7.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 8: Take note of the 4 boxed-up fields that you see below as you will need it in Step 10.

!Attachment Library^hanged8.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 9: Go to transaction SE37 and enter the function name RSPC_PROCESS_FINISH and execute it.

!Attachment Library^hanged9.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 10: Copy the values of the boxed-up fields of Step 8 and paste them into the fields below and for the field I_STATE, enter the value “G”. Then click execute.

!Attachment Library^hanged10.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 11: Return to the process chain log and refresh the log. The process after the “hanged” process should be running now. (if not, please let me know and I’ll analyze what happen and why it did not work for certain cases).

===========================================================================================================================

Errors in Loadings Concerning Flat Files

Error Description: An error in loading data from a flat file stored on WBP server.

Solution: Go to transaction code * L11* to verify the file and contact the related owners for the specific flow.

Step 1: In RSMO view the error message of the infopackage loading. In the following case, it was a invalid date data format.

!Attachment Library^PFFILE1.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 2: In * SMO*, under the tabe * eader*, look at the path of the file to identify where it is being stored.

!Attachment Library^PFFILE2.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 3: Go to transaction code * L11* and double click on the related directories to view the file.

!Attachment Library^PFFILE3.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 4: Capture screen shots of the actual problem and email to Guillaume to check who is the owner.

!Attachment Library^PFFILE4.JPG|cleanup="null" kids="null" pendingsrc="null" !

Step 5: nce the owner resolves the data file issue, repeat the loading again.

======================================================================================================================================h1. Steps to resolve the activation error in ODS_WBS7 =

The loading of ODS_WBS7 omes directly from RCS via the datasource WBS Elements: Commitment Line Items (0CO_OM_WBS_7)

Its update mode is in FULL and * ithout using the PSA*.

Therefore the method to solve the error is to do it via debugging mode.

The main steps are as follows.

View the attached file Steps to resolve activation error of ODS_WBS7 to view the steps with screen shots.

Step 1: In the main Daily Process Chain, right click on the errorneous local process chain as shown below and choose “Process Monitor” to view the detailed logs of this chain in order to find the errorneous process.

Step 2: dentify the erroneous process

Step 3: Right click on it and choose “Displaying Messages..”

Step 4: Scroll down to look for the error message and note down the field and values. In this case, the field is * _DINPD* and the value is * Boite de junction EExe 400x250x120”*. The error states that there is an error at the end of this value. Therefore we need to go to the data target to view and remove the invalid values.

Step 5: Go back to the error process and right click to choose “Administer Data Target”

Step 6: At the following screen, click on the tab “Contents”

Step 7: As data has not yet been activated successfully, it still resides in the New Data table. Therefore click on the button “New Data”.

Step 8: At the selection screen, look for the field * _DINPD* and input the values similar to what was stated in the error message with asterisks * in front and behind. Then click on execute button on the top left of the screen to continue.

Step 9: Click on the checkboxes to select both the records and click on the top left button to view the records in another screen.

Step 10: Type /h as shown below and press the Enter button on the keyboard twice slowly.

Step 11: In the debugger screen, double click on the word * ode* as shown below. By default, it will show you the value * HOW*.

Step 12: Change the value from * HOW* to * DIT*. * t has to be in uppercase alphabets.*Then click on the pencil button on the right to save the value. Then click on the button * 8*on the keyboard to continue.

Step 13: Now the fields are open for editing. Scroll down to the field and remove the trailing invalid values which in this case is the * ##*.

Step 14: Click on the save button on the top to save the changes. If there’s more than one record with errors, after saving the first changes, click on the top left button to go to the next record to do the same actions.

Step 15: Go back to the error process in the chain and right click on the erroneous process and choose “Repeat…” to run the activation again.

Leave the field as empty and click on the green tick button to continue.

Step 16: Click on the refresh button on the top as shown below to refresh the logs to show the repeated process which is in yellow which means that it is in progress.

Step 17: Note down the record and the field that has the invalid data and send and email to the relevant support team to request them to remove the invalid values from RCS to prevent such errors from happening the next data. In this case, it is finance data therefore the team to send to is * HD-RCS Support FA*.

=======================================================================================================================================