on 08-02-2016 7:15 PM
Dear eWM-Enthusiasts,
While confirming the WT for the IBDs, system is throwing this error "source data could not be changed" abruptly.
How to narrow down my search area , Where to pin-point the problem area faster ? Any power pointers in that directions will be appreciated ..
Only visible difference i notice is , we always handled 8 batches but first time we handled 12 batches ....should that matter ?
Best Regards
Monir
Hi,
what is it now? You confirm a WT (what your wrote in the initial message) or you create a WT (because everyone else is asking for the WT creation log)?
When you confirm a WT: can you show a screenshot of the WT and the WO?
Brgds
Juergen
---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/curriculum/scm_ewm
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Juergen,
Sorry , Original thread posting message was for confirmation ..... but now we have this error at WT creation stage .....
Below is the error message captured in the message log....
How to narrow down my search area , Where to pin-point the problem area faster ? Any power pointers in that directions will be appreciated ...
Message Text
Could not fully determine the destination data
Technical Data
Message type__________ E (Error)
Message class_________ /SCWM/PUT_BIN_DET (Messages: Bin Determination: Putaway)
Message number________ 054
Message variable 1____
Message variable 2____
Message variable 3____
Message variable 4____
Message Attributes
Level of detail_______
Problem class_________
Sort criterion________
Number________________ 1
Environment Information
Text (200 chars.)_____ /SCWM/ASP_TODLV_OI_HU
FieldName_____________
Field length 10_______ 0000000140
Regards
Monir
Dear Juergen,
The detailed message log is attached herewith...
Regards
Monir
I sorted the error based on message type Error , Success , Warnings etc.... before downloading .....
04.08.2016 Dynamic List Display 1
Type Message text LTxt Det.
***** HU WT Creation for HU 200003306702 *****
Storage control active for HU 200003306702 with storage process INB1
Storage process step IB03 determined for HU 200003306702
***** Determine source data - start *****
Source HU 200003306702 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306702
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
Capacity check against storage bin B044
Capacity determined from HU 200003306702
Weight: 1,409 KG are checked
against free capacity 999,999,999,999.999 KG with tolerance 0 KG
Volume: 1.00100000000000 M3 are checked
against free capacity 999,999,999,999.999 M3 with tolerance 0 M3
BADI: Putaway Bin B044 used in Determination
BADI: Door Bin DR04 successfully determined!
Storage bin B044 was found (storage type P001)
HU 200003306702 was checked successfully
Queue determination started with PLFJ/9030/OP02/ /1010/ / /PTWY
Queue determination number 00001 with /X/ /X/
Queue determined with PLFJ/ /OP02/ /1010/
Queue INBOUND_O1 determined
No unit of measure load category is assigned to HU type CPS
No entry maintained for whse process category 1 in whse number PLFJ
No storage bin access type maintained for storage bin 9030-PLF (PLFJ)
No storage bin access type maintained for storage bin B044 (PLFJ)
***** HU WT Creation for HU 200003306703 *****
Storage control active for HU 200003306703 with storage process INB1
Storage process step IB03 determined for HU 200003306703
***** Determine source data - start *****
Source HU 200003306703 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306703
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
Capacity check against storage bin B044
Capacity determined from HU 200003306703
Weight: 1,409 KG are checked
against free capacity 999,999,999,999.999 KG with tolerance 0 KG
Volume: 1.00100000000000 M3 are checked
against free capacity 999,999,999,999.999 M3 with tolerance 0 M3
Storage bin B044 was found (storage type P001)
HU 200003306703 was checked successfully
Queue determination started with PLFJ/9030/OP02/ /1010/ / /PTWY
Queue determination number 00001 with /X/ /X/
Queue determined with PLFJ/ /OP02/ /1010/
Queue INBOUND_O1 determined
No unit of measure load category is assigned to HU type CPS
No entry maintained for whse process category 1 in whse number PLFJ
No storage bin access type maintained for storage bin 9030-PLF (PLFJ)
No storage bin access type maintained for storage bin B044 (PLFJ)
***** HU WT Creation for HU 200003306704 *****
Storage control active for HU 200003306704 with storage process INB1
Storage process step IB03 determined for HU 200003306704
***** Determine source data - start *****
Source HU 200003306704 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306704
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
Capacity check against storage bin B045
Capacity determined from HU 200003306704
Weight: 1,409 KG are checked
against free capacity 999,999,999,999.999 KG with tolerance 0 KG
Volume: 1.00100000000000 M3 are checked
against free capacity 999,999,999,999.999 M3 with tolerance 0 M3
BADI: Putaway Bin B045 used in Determination
Storage bin B045 was found (storage type P001)
HU 200003306704 was checked successfully
Queue determination started with PLFJ/9030/OP02/ /1010/ / /PTWY
Queue determination number 00001 with /X/ /X/
Queue determined with PLFJ/ /OP02/ /1010/
Queue INBOUND_O1 determined
No unit of measure load category is assigned to HU type CPS
No entry maintained for whse process category 1 in whse number PLFJ
No storage bin access type maintained for storage bin 9030-PLF (PLFJ)
No storage bin access type maintained for storage bin B045 (PLFJ)
***** HU WT Creation for HU 200003306705 *****
Storage control active for HU 200003306705 with storage process INB1
Storage process step IB03 determined for HU 200003306705
***** Determine source data - start *****
Source HU 200003306705 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306705
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
Capacity check against storage bin B045
Capacity determined from HU 200003306705
Weight: 1,409 KG are checked
against free capacity 999,999,999,999.999 KG with tolerance 0 KG
Volume: 1.00100000000000 M3 are checked
against free capacity 999,999,999,999.999 M3 with tolerance 0 M3
Storage bin B045 was found (storage type P001)
HU 200003306705 was checked successfully
Queue determination started with PLFJ/9030/OP02/ /1010/ / /PTWY
Queue determination number 00001 with /X/ /X/
Queue determined with PLFJ/ /OP02/ /1010/
Queue INBOUND_O1 determined
No unit of measure load category is assigned to HU type CPS
No entry maintained for whse process category 1 in whse number PLFJ
No storage bin access type maintained for storage bin 9030-PLF (PLFJ)
No storage bin access type maintained for storage bin B045 (PLFJ)
***** HU WT Creation for HU 200003306706 *****
Storage control active for HU 200003306706 with storage process INB1
Storage process step IB03 determined for HU 200003306706
***** Determine source data - start *****
Source HU 200003306706 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306706
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
BADI: Bin Q058 blocked for Putaway and will be skipped
Could not fully determine the destination data
***** HU WT Creation for HU 200003306707 *****
Storage control active for HU 200003306707 with storage process INB1
Storage process step IB03 determined for HU 200003306707
***** Determine source data - start *****
Source HU 200003306707 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306707
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
BADI: Bin Q045 blocked for Putaway and will be skipped
Could not fully determine the destination data
***** HU WT Creation for HU 200003306708 *****
Storage control active for HU 200003306708 with storage process INB1
Storage process step IB03 determined for HU 200003306708
***** Determine source data - start *****
Source HU 200003306708 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306708
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
Could not fully determine the destination data
***** HU WT Creation for HU 200003306709 *****
Storage control active for HU 200003306709 with storage process INB1
Storage process step IB03 determined for HU 200003306709
***** Determine source data - start *****
Source HU 200003306709 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306709
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
BADI: Bin Q044 blocked for Putaway and will be skipped
Could not fully determine the destination data
***** HU WT Creation for HU 200003306710 *****
Storage control active for HU 200003306710 with storage process INB1
Storage process step IB03 determined for HU 200003306710
***** Determine source data - start *****
Source HU 200003306710 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306710
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
BADI: Bin Q047 blocked for Putaway and will be skipped
Could not fully determine the destination data
***** HU WT Creation for HU 200003306711 *****
Storage control active for HU 200003306711 with storage process INB1
Storage process step IB03 determined for HU 200003306711
***** Determine source data - start *****
Source HU 200003306711 entered; storage type: 9030; storage bin: 9030-PLF
Handling unit type CPS determined
Source storage bin 9030-PLF determined in storage type 9030
***** Determine destination data - start *****
Defaults for destination data: Handling Unit:00000000200003306711
Storage type search fully defined: No entry found
Storage type search with wild card: Search sequence PTW1 and rule 2 found
Storage type search sequence PTW1 found
Destination storage section check is not active in storage type P001
HU type check is not active in storage type P001
Alternatives during bin search: 1st alt. Stor.Bin Type, 2nd alt. Storage Sec., 3rd alt. StorType
Access table for bin search:
Storage type: P001 storage section: **** bin type: **** whse pos. eval.: 00000
Start of destination bin search
Stor.type: P001, stor.area: ****, bin type: ****, stock mvmt: 00000 being examined
Storage type P001: HU requirement
'Bulk' putaway behavior (storage type P001)
BADI: Bin Q048 blocked for Putaway and will be skipped
Could not fully determine the destination data
Dear All,
Thanks for being so kind & all the help.
Now im back to square one... now the problem that i reported in the original thread is back & haunting..
Below is the error message captured in the message log captured in foreground WT confirmation & not very detailed... In my case Source data comprises of Source Bin as doors...
05.08.2016 Dynamic List Display 1
Type Message text Det.
Source data could not be changed
Source data could not be changed
Source data could not be changed
Source data could not be changed
Source data could not be changed
Source data could not be changed
Source data could not be changed
Source data could not be changed
Source data could not be changed
Source data could not be changed
Source data could not be changed
Source data could not be changed
Debugging captures the error at the below code snippet with the value of the variables ...
* Check if Location has changed for Source HU
IF NOT cs_tap-vlenr IS INITIAL.
READ TABLE ct_huhdr ASSIGNING <huhdr>
WITH KEY huident = cs_tap-vlenr.
IF sy-subrc <> 0.
MESSAGE e829 WITH cs_tap-vlenr INTO gv_msgtext.
RAISE EXCEPTION TYPE /scwm/cx_core.
ENDIF.
IF ( <huhdr>-lgpla <> cs_tap-vlpla OR
<huhdr>-rsrc <> cs_tap-srsrc OR
<huhdr>-tu_num <> cs_tap-stu_num ) AND
cs_tap-gr_open IS INITIAL.
* Change of Source Data not allowed
MESSAGE e675 INTO gv_msgtext.
RAISE EXCEPTION TYPE /scwm/cx_core.
ENDIF.
ENDIF.
ENDIF.
variables values are
CS_TAP-VLPLA DR02
<HUHDR>-LGPLA 9030-PLF
CS_TAP-VLENR 00000000200003306690
<HUHDR>-TU_NUM
CS_TAP-STU_NUM
CS_TAP-GR_OPEN
100016127203 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A001 | DR02 | DR02 | 200003306699 | 200003306699 | |||
100016127204 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A001 | DR02 | DR02 | 200003306700 | 200003306700 | |||
100016127207 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A005 | DR02 | DR02 | 200003306695 | 200003306695 | |||
100016127208 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A005 | DR02 | DR02 | 200003306696 | 200003306696 | |||
100016127209 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A005 | DR02 | DR02 | 200003306697 | 200003306697 | |||
100016127210 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A005 | DR02 | DR02 | 200003306698 | 200003306698 | |||
100016127205 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A011 | DR02 | DR02 | 200003306693 | 200003306693 | |||
100016127206 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A011 | DR02 | DR02 | 200003306694 | 200003306694 | |||
100016127200 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A015 | DR02 | DR02 | 200003306690 | 200003306690 | |||
100016127201 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A015 | DR02 | DR02 | 200003306691 | 200003306691 | |||
100016127202 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A015 | DR02 | DR02 | 200003306692 | 200003306692 | |||
100016127211 | Confirm in Foreground | 1 | 1010 | OP01 | P001 |
A037 | DR02 | DR02 | 200003306701 | 200003306701 |
How to narrow down my search area , Where to pin-point the problem area faster ? Any power pointers in that directions will be appreciated ...
Regards
Monir
Hi,
While creating the WT system is finding the source as " Source storage bin 9030-PLF determined in storage type 9030 ".
But when the BAdi is executing the source bin is determined as " BADI: Door Bin DR04 successfully determined".
This is a mismatch in BAdi execution and the original source ( storage bin 9030-PLF ) is subjected to POSC, since your HU is activated for the storage control.
BR,
C K Reddy
When you try to create the warehouse task and get the error message, close the message box and press the Message Log button on the application tool bar (SHIFT + F12).
This will show you a full log and should display the error with additional detail.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Anoop & Andy,
Many thanks for the help....
Below is the error message captured in the message log....
How to narrow down my search area , Where to pin-point the problem area faster ? Any power pointers in that directions will be appreciated ...
Message Text
Could not fully determine the destination data
Technical Data
Message type__________ E (Error)
Message class_________ /SCWM/PUT_BIN_DET (Messages: Bin Determination: Putaway)
Message number________ 054
Message variable 1____
Message variable 2____
Message variable 3____
Message variable 4____
Message Attributes
Level of detail_______
Problem class_________
Sort criterion________
Number________________ 1
Environment Information
Text (200 chars.)_____ /SCWM/ASP_TODLV_OI_HU
FieldName_____________
Field length 10_______ 0000000140
Regards
Monir
User | Count |
---|---|
9 | |
4 | |
3 | |
2 | |
2 | |
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.