cancel
Showing results for 
Search instead for 
Did you mean: 

CCR Error 381/ 282

b_valavan
Participant
0 Kudos

Hi,

Recently we upgraded to SCM 5.1

When CCR is done for stock we get a strange error 381 & 382. Error shown in two categories. This happens only for Batch stock with Restricted use.

Product A - with CCR error 381 ( Missing in APO)

When this is pushed to APO, Restriced stock ( CK) is displayed in APO but error remains after iteration. It also throws susequent error for the same product A with error code 382 - Not in R3 and system ask me to delete in APO.

Note : At this stage CK stock for product A is available in both R3 and APO.

have anyone came across the same situation ? Let me knw how to resolve this.

Regards

BVN

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Valavan,

1) Please check whether the stocks in restricted area are defined as available

in R/3 customisation. (under MRP > Planning > MRP calculation > stocks >

define availability)

2) Check in CFc9 transaction, check whether the re-read indicator is active

3) Check the enhancments for stocks under R/3 customisation.

Regards

R. Senthil Mareeswaran.

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi BVN,

Since this stock reported by CCR as not in R/3 please check if it is directly uploded into APO.

This will always show as qty in R/3 as zero and some times ccr will report error code as 381/382

Rgds

SB

Former Member
0 Kudos

Hi Valavan,

1) Could you please check whether all your integration models for

stock, batches are active.

2) stocks are available in defined storage locations and in

unrestricted area in R/3

3) No queues and sysfails

Confirm your findings

Regards

R. Senthil Mareeswaran.

b_valavan
Participant
0 Kudos

Senthil,

1. My integration model for stock is active .

2. Stocks available in defined storage locations but in restricted use. But my batch stock is in Restricted use. Is that the rootcause for this ? In my earlier release i din come across this error .

3. No que blockage.

We see this error only after upgrade to SCM 5.1

Regards

BVN

Edited by: B Valavan on Aug 13, 2009 9:54 AM

Edited by: B Valavan on Aug 13, 2009 9:55 AM