INSTANCE NAME IC1(SAP LABS INSTANCE)

VERSION ECC 4.6 C

We are carrying out following steps. 1) Create ECN1 (CCAP_ECN_CREATE). 2) Create Routing with change number 1 (BAPI_ROUTING_CREATE). 3) Change valid from and alternate date of ECN1 (CCAP_ECN_MAINTAIN). Input data for the same is provided as,

CCAP_ECN_CREATE
CHANGE_HEADER CHANGE_NO STATUS VALID_FROM DESCRIPT REASON_CHG OBJECT_TLIST ACTIVE OBJ_REQU MGTREC_GEN FL_COMMIT_AND_WAIT ALT_DATES ALT_DATE VALID_FROM BAPI_ROUTING_CREATE

W1901E1 1 3001-12-31
TEST FOR RTG EFF PROCESS

X X X X 2009-0119(CURRENT DATE) 3001-12-31

TASK
TASK_LIST_GROUP GROUP_COUNTER CHANGE_NO TASK_LIST_USAGE PLANT TASK_LIST_STATUS TASK_MEASURE_UNIT

W1901G1 01 W1901E1 1 1100 4 EA W1901G1 01 W1901E1 0010 PP01

OPERATION
TASK_LIST_GROUP GROUP_COUNTER CHANGE_NO ACTIVITY CONTROL_KEY

WORK_CNTR PLANT OPERATION_MEASURE_UNIT DENOMINATOR NOMINATOR BASE_QUANTITY

1100 1100 EA 1 1 12 W1901G1 01 W1901E1 0020 PP01 1100 1100 EA 1 1 12 W1901G1 01 ALT1 W1901E1 2 0 0010 0020 X

OPERATION
TASK_LIST_GROUP GROUP_COUNTER CHANGE_NO ACTIVITY CONTROL_KEY WORK_CNTR PLANT OPERATION_MEASURE_UNIT DENOMINATOR NOMINATOR BASE_QUANTITY

SEQUENCE
TASK_LIST_GROUP GROUP_COUNTER SEQUENCE_NO CHANGE_NO SEQUENCE_CATEGORY REFERENCE_SEQUENCE BRANCH_OPERATION RETURN_OPERATION BAPI_TRANSACTION_COMMIT

Following are screenshots of Routing (output after BAPI_ROUTING_CREATE) Through GUI (CA03).

CCAP_ECN_MAINTAIN CHANGE_HEADER CHANGE_NO STATUS VALID_FROM DESCRIPT REASON_CHG OBJECT_TLIST ACTIVE OBJ_REQU MGTREC_GEN FL_COMMIT_AND_WAIT

W1901E1 1 2009-01-19 (current date)

TEST FOR RTG EFF PROCESS

FL_SYNCH
ALT_DATES ALT_DATE

X X X X X X 2010-01-19(future

VALID_FROM OBJMRC ALT_DATE CHG_OBJTYP CHGTYPEOBJ TLIST_TYPE TLIST_GRP

date) 2010-01-19 (future date) 2010-01-19 (future date) 2

900 N

W1901G1

CA03 AFTER CCAP_ECN_MAINTAIN (observe valid from).

After this we are carrying out following steps. 1) Create ECN2 (CCAP_ECN_CREATE). 2) Modify routing with ECN2 by Tr code CA02 (say: add one new operation and modify some attributes of existing operation). 3) Change valid from and alternate date of ECN1 (CCAP_ECN_MAINTAIN). Following is the input data for above-mentioned steps.

CCAP_ECN_CREATE
CHANGE_HEADER CHANGE_NO STATUS VALID_FROM DESCRIPT REASON_CHG OBJECT_TLIST ACTIVE OBJ_REQU MGTREC_GEN FL_COMMIT_AND_WAIT ALT_DATES ALT_DATE VALID_FROM

W1901E2 1 3001-1231(future date)

TEST FOR RTG EFF PROCESS

X X X X 2009-0119(current date) 3001-1231(future date)

After creating this ECN2 we are modifying routing through CA02. Say: add operation (0030) and change some attributes of existing operation (0010).

Now in modification of ECN we provide following data.

CCAP_ECN_MAINTAIN CHANGE_HEADER CHANGE_NO STATUS VALID_FROM DESCRIPT REASON_CHG OBJECT_TLIST ACTIVE OBJ_REQU MGTREC_GEN FL_COMMIT_AND_WAIT

A1401E2 1 2009-01-19 (current date)

TEST FOR RTG EFF PROCESS

X X X X X

ALT_DATES ALT_DATE VALID_FROM OBJMRC ALT_DATE CHG_OBJTYP CHGTYPEOBJ TLIST_TYPE TLIST_GRP

2010-01-19(future date) 2010-01-19 date) 2010-01-19(future date) 2

900 N

W1901G1

After executing this we get following screen, which shows an exception.

And we observed following explanation of exception in SLG1.

But if we execute same set of steps on SAP LABS CF5 (ECC 6.0) instance ,All these work fine. We dont get any error and we are able to see our routing with required Date changes. So do we need to apply any patch for this application?