SD_DELIVERY_UPDATE_PICKING
Hi,
My problem is: I am using the BAPI SD_DELIVERY_UPDATE_PICKING to update the quantity of items from a consignment that comes from an interface XI. For example: The amount registered this with 10, after, I run the BAPI with quantity 15. In the end, when I go back to view, is the amount of 25, or the quantities were added. Someone can help me?
Thank's a lot.
Hello,
if have got the same problem. I try to explain it by an example: I have got a delivery with a delivery quantity of 10 pieces.I use the function module SD_DELIVERY_UPDATE_PICKING to set the picking quantity, lets say also 10 pieces. For any reason I have to change the picking quantity again, lets say to 5 pieces. When I use the FM SD_DELIVERY_UPDATE_PICKING to set the picking quantity again, I got 15 pieces, because the amounts are added together.Is there a way to supress this behaviour in the FM?
Regards
Henryk
Edited by: Henryk Eimler on Mar 25, 2010 1:13 PM
Similar Messages
-
Transfer Orders - SD_DELIVERY_UPDATE_PICKING
We currently have a BDC into LT03 which we want to replace with a function module call. I found function module SD_DELIVERY_UPDATE_PICKING and I have it working to some extent. I have it updating the deliveries pick qty, but it does not create a transfer order. I was hoping the function module would create a transfer order that would move the material from the current location to location of delivery. But I have had no luck passing in parameters to make that happen. So is this functionality available with SD_DELIVERY_UPDATE_PICKING or do I have to find additional function module.
Thanks
Matthew> Hi Matthew,
>
> Please refer to the following post.
>
> Creating/confirming transfer order (WM) using bapi/function modules
>
> Thanks
> Vinod
I will have to L_TO_CREATE_DN a try. So I am starting to guess that the SD_DELIVERY_UPDATE_PICKING requires a transfer order already created that it will confirm. But I will have to try that.
Thanks.
Matthew -
Can I use SD_DELIVERY_UPDATE_PICKING to change the delivery qty?
hi experts,
I have used SD_DELIVERY_UPDATE_PICKING to updating the picking quantity in a delivery document and post goods issue. also want to use the FM to change the delivery qty ,when the picking qty < delivery qty ; and do the post goods issue automatic .
and i find the field :
VBPOK-LIANP *Change delivery quantity
i do like this ,when VBPOK-LFIMG > VBPOK-PIkMG ,
VBPOK-LIANP = 'X'.
VBPOK-LFIMG = VBPOK-PIkMG
but the FM also can't change delivery qty.
please help me !Hi,
We need only Delivery Number and its item for picking. I am not clear with what reference number you were referring to.
Thanks, -
Dont want to do the conversion in SD_DELIVERY_UPDATE_PICKING
Hi My requirement is i need to update the picking quantity in delivery document,
For this iam Using SD_DELIVERY_UPDATE_PICKING the function module.Iam using a custom screen .
In this iam picking the delivery but when the materials UOM and SU is different it is not doing the conversions.
But i dont want to do the converions,.
How to do this.
Regards,
Vinay.Hi,
With the help of basis team carry out authorization for change object.
T-code SU24 >>> Put code VL01N >>> Execute,
You will get authorization object list for this perticular transaction.
Kapil -
Picking with SD_DELIVERY_UPDATE_PICKING
Hello,
I am using function module SD_DELIVERY_UPDATE_PICKING to pick delivery items. This FM is being called in a loop for each delivery item. Delivery has two items, and each item has to be picked in two batches. This FM call is working fine if there is only one item in delivery. When delivery with two items are processed, 2nd item throws error message as "Item 900003: Only 0 qty from material xxxx are available". But when I check the delivery after the FM call, it shows first item as picked correctly under two batches.
Here I have showed the code I am using to call FM.
Loop at delivery_itab.
wa_vbkok-vbeln_vl = wa_e1edl20-vbeln.
wa_vbkok-wadat_ist = lv_pgidate.
wa_vbpok-vbeln = wa_e1edl20-vbeln.
wa_vbpok-posnn = wa_e1edl24-posnr.
wa_vbpok-vbeln_vl = wa_e1edl20-vbeln.
wa_vbpok-posnr_vl = wa_e1edl24-posnr.
wa_vbpok-charg = wa_e1edl24-charg.
wa_vbpok-matnr = wa_e1edl24-matnr.
wa_vbpok-vbtyp_n = 'J'.
wa_vbpok-taqui = 'X'.
APPEND wa_vbpok TO lt_vbpok.
...For each delivery item...
CALL FUNCTION 'SD_DELIVERY_UPDATE_PICKING'
EXPORTING
vbkok_wa = wa_vbkok
synchron = 'X'
nicht_sperren = 'X'
if_error_messages_send = 'X'
TABLES
vbpok_tab = lt_vbpok
prot = lt_prot.
Endloop.
I also tried function module WS_DELIVERY_UPDATE in the same place of code. That also gives the same issue. I tried WS_DELIVERY_UPDATE as showed below.
CALL FUNCTION 'WS_DELIVERY_UPDATE'
EXPORTING
vbkok_wa = wa_vbkok
synchron = 'X'
commit = 'X'
delivery = wa_vbkok-vbeln_vl
update_picking = 'X'
TABLES
vbpok_tab = lt_vbpok
prot = lt_prot
EXCEPTIONS
error_message = 99.
Also I tried to call the FM with all the delivery items appended in itab lt_vbpok. That doesn't work, gives the same error message. I have also taken care to wait until delivery update is commited. Also I am doing Enque and Deque for the delivery document.
Can you pls suggest me if I am missing any parameters / any thing here ? I would greatly appreciate your help.
Thanks
HariHi ,
Try this way
Step 1
loop at tvblkp.
hvbpok-vbeln_vl = tvblkp-vbeln.
hvbpok-posnr_vl = tvblkp-posnr.
hvbpok-posnn = tvblkp-posnr.
hvbpok-vbeln = vblkk-komau.
hvbpok-vbtyp_n = 'Q'.
hvbpok-pikmg = tvblkp-komng.
hvbpok-meins = tvblkp-meins.
hvbpok-ndifm = 0.
hvbpok-taqui = ' '.
if tvblkp-posnr > '900000' and not tvblkp-uecha is initial.
hvbpok-taqui = 'X'.
endif.
hvbpok-charg = tvblkp-charg.
hvbpok-matnr = tvblkp-matnr.
hvbpok-brgew = tvblkp-brgew.
hvbpok-gewei = tvblkp-gewei.
hvbpok-volum = tvblkp-volum.
hvbpok-voleh = tvblkp-voleh.
hvbpok-orpos = 0.
append hvbpok.
endloop.
*--call FM after the loop.
Step 2 .
sav_nast = nast.
call function 'SD_DELIVERY_UPDATE_PICKING'
exporting
nicht_sperren = 'X'
vbkok_wa = vbkok
aufrufer_t = 'X'
if_error_messages_send = ' '
tables
vbpok_tab = hvbpok
prot = lt_prot.
Regards,
Vind -
SD_DELIVERY_UPDATE_PICKING batch split
Hi
If there is a batch split in a delivery and automatic batch determination with print picking list send time (V_TVST-VSZTP) : 4 (Send immediately (when saving the application)) picking quantities are copied to main item but not to the batch split items.
Example:
Item LFIMG PIKMG
000010 0,00 7,00
900001 4,00 0,00
900002 3,00 0,00
In this case batch split items picking status (VBUP-KOSTA) stays A-Not yet picked. So the delivery document can not be posted goods issue.
I am looking for a way to change the example as follows:
Item LFIMG PIKMG
000010 0,00 0,00
900001 4,00 4,00
900002 3,00 3,00
Is there any way to copy the picking quantities to the batch items?
thanksHi Kemal.
How you resolved this problem ?
Regards,
Manuel H, -
Urgent help needed-Updating an outbound delivery.
Hi,
I have created an outbound delivery for a stock transport order in using VL10D.
The otbound delivery then goes to a different system wherein it is updated with picking,packing and shipping info.Then it comes back to SAP in the form of idoc(DELVRY05).Now what I need is to write a code in an exit(I know where to write the code) from where the data in the idoc will update the outbouned delivery with picked and delivered quantity.
I tried using FM's SD_DELIVERY_UPDATE_PICKING and WS_DELIVERY_UPDATE_2 but it is not working.Also where will I get to see the update if it happens.
Please help me.Its required urgently.
Thanks,
Sandeep.Sandeep,
I m trying to understand this requirement. Your IDOC comes in with updated information for a delivery thats already available in the system.
In this case, the IDOC would lock the delivery object for its ude, so writing FM's directly might not help.
Please let me know your process code or your inbound FM. If it is IDOC_INPUT_DELVRY, then it already uses a WS_DELIVERY_UPDATE_2 , so there is little reason why you should be calling the FM again.
Please note that when this comes in it creates an inbound delivery rather an outbound. So, is your third party system sending you back an outbound IDOC?
Do you want to update the delivery that u sent out ( SD) to the third party system from that information.
In that case, please use BAPI_OUTB_DELIVERY_CONFIRM_DEC. This is for delivery conformation from a third party system. The documentation is very clear and there are toms of examples on SDN.
Please reward if useful.
Thanks
Ganesh.S -
Post Goods Issue for Outbound delivery return
Hi, I'm trying to Post a Goods Issue for a returned outbound delivery but I cannot find a function module to do this, I tried using SD_DELIVERY_UPDATE_PICKING but its creating the material against the outbound delivery with status archived, which means it wasn't created.
I also tried using the MB_CREATE_GOODS_MOVEMENT, but this one is creating the material document but not updating the status and the document flow of the delivery.
Thanks,
PabloHi Lopez,
Post Goods Issue with MB_CREATE_GOODS_MOVEMENT FM in VL02N
Regards,
Sravanthi -
Urgent-Help needed in FM to update picking quantity in outbound delivery.
Hi,
I have to automatically update the delivery and picking quantity for an outbound delivery without doing any post goods issue.Could you please help me with any FM which does this with proper explanation.
Any help will be greatly appreciated.
Thanks,
Sandeep.Check with FM : SD_DELIVERY_UPDATE_PICKING
The above FM will update Picking in delivery
Check the structure VBPOK ,within structure VBPOKKOMMI(Include structure)
Field is PIKMG.
Thanks
Seshu -
Create delivery automatically when sales order is created but not invoice??
Hi,
I have a requirement where in, it should create delivery (also issue) automatically when i create sales order, but it should not create the invoice automatically. I am going to do the invoice manually from the delivery document. Can you suggest me how to do this??
Thanks
GhaneshHi,
If the sales document type is not relavant for Cash sale and the document type is used globally in the business then if for some specific conditions like distribution channel or plant or for division if u want to carry out the immediate delivery creation and PGI, use the below user exits and Bapi's
The below user exit is used to export the sales order details to capture the required checking cond such as sal org,dist ch,div,plant,etc
Include MV45AFZZ
FORM USEREXIT_SAVE_DOCUMENT.
Include MV45AFZA
FORM -USEREXIT_REFRESH_DOCUMENT.
BAPI_ISAORDER_GETDETAILEDLIST
BAPI_OUTB_DELIVERY_CREATE_SLS
SD_DELIVERY_UPDATE_PICKING
BAPI_OUB_DELIVERY_CONFIRM_DEC
Regards,
Gopal. -
Hi gurus,
I got short dump CALL_FUNCTION_CONFLICT_LENG .
could you please suggest me how to rectify this problem?
Please find the below runtime error details.
Runtime Error CALL_FUNCTION_CONFLICT_LENG
Exception CX_SY_DYN_CALL_ILLEGAL_TYPE
Occurred on 15.12.2008 at 12:00:23
Type conflict when calling a function module (field length).
What happened?
Error in ABAP application program.
The current ABAP program "SAPLZDELVCONF" had to be terminated because one of
the
statements could not be executed.
This is probably due to an error in the ABAP program.
A function module was called incorrectly.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE',
was neither
caught nor passed along using a RAISING clause, in the procedure
"ZIDOC_INPUT_ZDELVCONF" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The call to the function module "BAPI_OUTB_DELIVERY_CONFIRM_DEC" is incorrect:
In the function module interface, you can specify only
fields of a specific type and length under "HEADER_CONTROL".
Although the currently specified field
"V_BAPIOBDLVHDRCTRLCON" is the correct type, its length is incorrect.
How to correct the error
The exception must either be prevented, caught within the procedure
"ZIDOC_INPUT_ZDELVCONF"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CALL_FUNCTION_CONFLICT_LENG" CX_SY_DYN_CALL_ILLEGAL_TYPEC
"SAPLZDELVCONF" or "LZDELVCONFU01"
"ZIDOC_INPUT_ZDELVCONF"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
If the error occurs in the program SAPCNVE, it could be for any of
the following reasons:
1. The field <INPUT> conflicts with a function module called
"..._INPUT" or the field <OUTPUT> with "..._OUTPUT".
This is probably due to an error in the definition of the
function module interface. For the relevant
parameters, you should not specify any reference field.
2. The field <INPUT> conflicts with a function module called
"..._OUTPUT".
It may be that the GPA mechanism was used to read a value from the
SAP memory with an incorrect length. The
material number conversion MATN1, for example, expects
a material number 18 characters long in ABAP/4 internal terms. If,
instead, MAT contains a value only 1 character long, the program
terminates.
To view the current contents of the SAP memory, go into "Debugging"
and select Goto -> System -> System areas. View area SMEM.
A GPA value may be the wrong length for any of the following reasons:
a) The user master record contains a value with an incorrect length.
b) In the current transaction, an incorrect parameter ID was
chosen for the field with this conversion.
c) In one of the screens for a previously executed transaction, a
field was assigned an incorrect parameter ID.
d) In a previously executed ABAP/4 program, a
SET-PARAMETER statement has a value with an incorrect length, e.g.
SET PARAMETER ID 'MAT' FIELD '1'.
System environment
SAP Release.............. "620"
Application server....... "efcuxp01"
Network address.......... "10.94.10.43"
Operating system......... "HP-UX"
Release.................. "B.11.23"
Hardware type............ "ia64"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 23
Short dump setting....... "full"
Database server.......... "efcuxp1t"
Database type............ "ORACLE"
Database name............ "P60"
Database owner........... "SAPR3"
Terminal................. " "
Character set............ "C"
SAP kernel............... "640"
Created on............... "Oct 26 2008 20:48:43"
Created in............... "HP-UX B.11.23 U ia64"
Database version......... "OCI_920 "
Patch level.............. "257"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
User, transaction...
Client.............. 100
User................ "BATCHUSER"
Language key........ "E"
Transaction......... " "
Program............. "SAPLZDELVCONF"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLZDELVCONF" in
"ZIDOC_INPUT_ZDELVCONF".
The main program was "RBDAPP01 ".
The termination occurred in line 167 of the source code of the (Include)
program "LZDELVCONFU01"
of the source code of program "LZDELVCONFU01" (when calling the editor 1670).
The program "SAPLZDELVCONF" was started as a background job.
Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_TYPE"
occurred in the
procedure "ZIDOC_INPUT_ZDELVCONF" "(FUNCTION)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLZDELVCONF ". Its source code starts in
line 5
of the (Include) program "LZDELVCONF$01 ".
Source code extract
001370 l_bapiobdlvitemctrlcon.
001380 l_bapiobdlvitemctrlcon-deliv_numb = v_delv_no.
001390 APPEND l_bapiobdlvitemctrlcon TO t_bapiobdlvitemctrlcon.
001400 ENDCASE.
001410 ENDLOOP.
001420 ENDLOOP. "End loop at idoc_contrl.
001430
001440 * Populate Picking Qty into delv item line, those belong item
001450 * category 'KBN'
001460 IF NOT t_vbpok IS INITIAL.
001470 * Call FM to update picking QTY
001480 CALL FUNCTION 'SD_DELIVERY_UPDATE_PICKING'
001490 EXPORTING
001500 vbkok_wa = l_vbkok
001510 * SYNCHRON = ' '
001520 * NO_MESSAGES_UPDATE = ' '
001530 * NICHT_SPERREN = ' '
001540 * AUFRUFER_T = ' '
001550 * IF_ERROR_MESSAGES_SEND = 'X'
001560 TABLES
001570 vbpok_tab = t_vbpok
001580 prot = t_prot.
001590 * Check Picking QTY successfully update
001600 IF t_prot IS INITIAL.
001610 * Commit
001620 COMMIT WORK.
001630 ENDIF.
001640 ENDIF.
001650
001660 * Call FM to confirm Delivery
> CALL FUNCTION 'BAPI_OUTB_DELIVERY_CONFIRM_DEC'
00168 0 EXPORTING
001690 header_data = v_bapiobdlvhdrcon
001700 header_control = v_bapiobdlvhdrctrlcon
001710 delivery = v_delv_no
001720 TABLES
001730 item_data = t_bapiobdlvitemcon
001740 item_control = t_bapiobdlvitemctrlcon
001750 return = t_bapiret2.
001760 IF t_bapiret2[] IS INITIAL.
001770 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
001780 IMPORTING
001790 return = l_bapiret2.
001800 IF l_bapiret2 IS INITIAL.
001810
001820
001830 *{ INSERT D60K962623 T.Jain
001840 * Update LIKP-VLSTK as blank in database table.
001850
001860
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM
SY-TITLE Inbound Processing of IDocs Ready for Transfer
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
7 FUNCTION ZIDOC_INPUT_ZDELVCONF
SAPLZDELVCONF
LZDELVCONFU01 167
6 FORM IDOCS_PASS_TO_APPLICATION
SAPLBD20
LBD20F0A 367
5 FORM IDOCS_PROCESS
SAPLBD20
LBD20F0B 68
4 FUNCTION IDOC_INPUT
SAPLBD20
LBD20U05 240
3 FUNCTION IDOC_START_INBOUND
SAPLEDIR
LEDIRU02 163
2 FUNCTION APPLICATION_IDOC_POST_IMMEDIAT
SAPLBD12
LBD12U04 37
1 EVENT START-OF-SELECTION
RBDAPP01
RBDAPP01 327
Chosen variables
7 FUNCTION ZIDOC_INPUT_ZDELVCONF
SAPLZDELVCONF
LZDELVCONFU01 167
INPUT_METHOD
0
0
2
0
MASS_PROCESSING X
0
0
5
8
APPLICATION_VARIABLE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
CALL_TRANSACTION_DONE
0
0
2
0
DOCUMENT_NUMBER
0000000000
0000000000
2222222222
0000000000
IN_UPDATE_TASK
0
0
2
0
WORKFLOW_RESULT
00000
00000
22222
00000
EDI_TEXT[] Table[initial]
EDI_TEXT_LINES[] Table[initial]
IDOC_CONTRL[] Table IT_96[1x1084]
IDOC_DATA[] Table IT_97[113x2122]
IDOC_STATUS[] Table IT_105[0x788]
RETURN_VARIABLES[] Table IT_106[0x204]
SERIALIZATION_INFO[] Table IT_107[0x430]
T_BAPISDH1X
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
00000000000000000000
00000000000000000000
22222222222222222222
00000000000000000000
T_PROT Table[initial]
V_STO
0000000000
0000000000
2222222222
0000000000
T_VBPOK Table[initial]
%_ARCHIVE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
SY-ONCOM S
0
0
5
3
I_EMSEG[] Table[initial]
V_DELV_NO 0720010737
0000000000
0000000000
3333333333
0720010737
I_IMSEG 00000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333333322222222222222222222222222
0000000000000000000000000000000000000000
... + 40 #
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222220222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 #### #### #### 00000 0
0000000000000000000000000000000000000000
0000C000000C000000C000000000000000000000
2000022200002220000222222222222233333232
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 000000000
000000000000000
000000000000000
222222333333333
000000000000000
V_BAPIOBDLVHDRCTRLCON 0720010737
0000000000000000000000000000000
0000000000000000000000000000000
3333333333222222222222222222222
0720010737000000000000000000000
I_IMSEG[] Table[initial]
V_BAPIOBDLVHDRCON 0720010737######## ####
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333000000002222220000222222222222
0720010737000C000C000000000C000000000000
... + 40 00
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222223322
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000
0000000000000000000000000
2222222222222222222222222
0000000000000000000000000
I_IMKPF 0000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333333333222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 0
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222322222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
00
00
22
00
T_BAPIOBDLVITEMCTRLCON Table IT_109[55x42]
I_EMSEG 00000000000000##000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333333300333333333333222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 00
000000000000000
000000000000000
222222222222233
000000000000000
T_BAPIOBDLVITEMCON Table IT_108[55x440]
I_EMKPF 000000000000000000 ##
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222333333333333333333222222222200
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
T_BAPIRET2 Table[initial]
SYST-REPID SAPLZDELVCONF
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454544454444222222222222222222222222222
310CA45C63FE6000000000000000000000000000
6 FORM IDOCS_PASS_TO_APPLICATION
SAPLBD20
LBD20F0A 367
SY-XFORM CONVERSION_EXIT
000000000000000000000000000000
000000000000000000000000000000
444545544454545222222222222222
3FE65239FEF5894000000000000000
SY-REPID SAPLBD20
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454443322222222222222222222222222222222
310C242000000000000000000000000000000000
SY-MSGID
00000000000000000000
00000000000000000000
22222222222222222222
00000000000000000000
C_WF_RESULT_OK 0
00000
00000
32222
00000
SPACE
0
0
2
0
SY-MSGNO 000
000
000
333
000
SY-MSGV1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000
0000000000
2222222222
0000000000
SY-MSGV2
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000
0000000000
2222222222
0000000000
SY-MSGV3
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000
0000000000
2222222222
0000000000
SY-MSGV4
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000
0000000000
2222222222
0000000000
PI_INPUT_METHOD
0
0
2
0
EDIFCT
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
000000000000000000
000000000000000000
222222222222222222
000000000000000000
PIF_EVENT_INFO-FUNCNAME ZIDOC_INPUT_ZDELVCONF
000000000000000000000000000000
000000000000000000000000000000
544445445555544454444222222222
A94F3F9E054FA45C63FE6000000000
C_WF_PAR_APPL_OBJECTS Appl_Objects
00000000000000000000000000000000
00000000000000000000000000000000
47765466667722222222222222222222
100CFF2A534300000000000000000000
C_WF_PAR_CREATED_OBJECTS Appl_Objects
00000000000000000000000000000000
00000000000000000000000000000000
47765466667722222222222222222222
100CFF2A534300000000000000000000
PI_MASS_PROCESSING X
0
0
5
8
SY-XPROG SAPCNVE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
PE_APPLICATION_VARIABLE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
PE_CALL_TRANSACTION_DONE
0
0
2
0
PE_IN_UPDATE_TASK
0
0
2
0
%_ARCHIVE
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
000000000000000
000000000000000
222222222222222
000000000000000
PE_WORKFLOW_RESULT
00000
00000
22222
00000
SYST-SUBRC 0
0000
0000
PXT_IDOC_CONTROL[] Table IT_96[1x1084]
C_WF_PAR_APPL_OBJ_TYPE Appl_Object_Type
00000000000000000000000000000000
00000000000000000000000000000000
47765466667557762222222222222222
100CFF2A534F49050000000000000000
PXT_IDOC_DATA[] Table IT_97[113x2122]
T_APPL_IDOC_STATUS[] Table IT_105[0x788]
PET_RETURN_VARIABLES[] Table IT_106[0x204]
T_SERIALIZATION_INFO[] Table IT_107[0x430]
5 FORM IDOCS_PROCESS
SAPLBD20
LBD20F0B 68
PIT_IDOC_STATUS 000000001561906062IB1 0
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3333333333333333334432222222222222222223
0000000015619060629210000000000000000000
... + 40 42
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
3322222222222222222222222222222222222222
4200000000000000000000000000000000000000
... + 80
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... +Hi,
Try to use SO_CONVERT_OBJECT_TO_FAX.
Reward If UsefuL -
COMMIT WORK - performance problem
Dear Fellow SDNers,
I seek your help on the following problem:
Scenario : Inbound idoc which updates an Outbound delivery with Picked quantity, posts the goods issue and then creates billing document
Approach : I am using the function module SD_DELIVERY_UPDATE_PICKING to update the delivery from the idoc data and to post goods issue. Thereafter, i use BAPI_BILLINGDOC_CREATEMULTIPLE to create the billing document. Before calling this BAPI, I use a COMMIT WORK statement to update the relevant tables so as to enable invoice creation properly.
Problem: The COMMIT WORK statement takes a lot of time to execute (I have no update tasks that could lead to this), so much that the idoc (probably) has a timeout and ends up in status 64. As a result, the succeeding part of the code (after COMMIT WORK) is not executed and the billing document is not created.
When I debug this, the COMMIT WORK statement leads to a strange screen (which looks like a blank report output screen, with its title as "UPDATE CONTROL". However (of course), there is no timeout while debugging and the billing document is successfully created.
Could anyone provide some pointers to solve this problem?
regards,
Priyanki have a custom function module Y_IDOC_INPUT_WMSPICK001 which is responsible for idoc inbound processing. SAP PI sends the inbound data to ECC and once this is done, this function module is executed.
This FM has the following code sequence inside it...
1) Call the FM SD_DELIVERY_UPDATE_PICKING
2) COMMIT WORK AND WAIT.
3) Call the BAPI_BILLINGDOC_CREATEMULTIPLE
Step1 is successfully executed, the step 2 takes a long time, and after that, the step 3 is not executed at all and the idoc ends up with a yellow light (status 64).
hope it clarifies what I am doing
regards,
Priyank -
Picked Quantity is not updated After delivery in Vl03n
After delivey in Order (VA03), the picked quantity is not updated Properly(VL03n). It is coming as Zero.
Is it any configurations needed or writng any code.
For that I put Break point in FMs like SD_DELIVERY_UPDATE_PICKING in program RVADEK01.
But it is not stopping the Program.
Please give any possible solution.Hi Vinod,
Thank u For ur Answer.
Just my Fuctional Consultant given Procedure.
How to test the picking list. The problem is after Deliver the Order quantity in VA03 and after saving, this will creates One Out Bound delivery.
Now We r checking VL03n. Now it is updating the Picked Quantity Correctly, For that We r using the Standard Print program: RVADEK01, Form: RVPICSKSIN.
Output Type: EK00, Application: V4.
Here My problem is We copied the Form and print Program and modified according to our requirement and they configured in Nace with our own Output type. We haven't chenged the updated Functionality and Not even Standard program. We wrote some include program for getting new values in scripts.
Now the picked quantity is not updated after picking in VL03n. -
Error occuring when calling a function via BSP
In BSP, I call the function 'SD_DELIVERY_UPDATE_PICKING' to update a delivery. Unfortunately, when there is an error during processing this function (it is returned in the export table PROT), I found that this delivery is always locked! On the other hand, calling this function in SAP GUI, I haven't found this problem. How can I solve it. I try to use the command 'commit work.', but it doesn't work.
Moreover, when this function raises an error message, in SAP GUI this function terminates its work according to the message type 'E' rule. However, in BSP, when this error message is raised, the page shows 'The page cannot be displayed'. How can I solve these problems.you should do something like below.
call function 'SD_DELIVERY_UPDATE_PICKING'
exporting
vbkok_wa = <vbkok_wa>
synchron = ' '
no_messages_update = ' '
tables
vbpok_tab = tvbpok
prot = wat_prot
exceptions
error_message = 2.
case sy-subrc.
when 0.
describe table wat_prot lines fa_lines.
if fa_lines = 0.
commit work.
else.
* fill a vairable with a message and show it in BSP page
endif.
when 2.
Regards
Raja -
Need a FM for change delivery quantity
Hello,
I need a FM to update delivery quantity, I have look for the BAPI BAPI_OUTB_DELIVERY_CONFIRM_DEC but I didn't find how it works.
Any help are welcome
FrédéricHi,
I need a SAP FM to update the delivery quantity and the pick quantity, if pick quantity is different than the delivery quantity. I tried SD_DELIVERY_UPDATE_PICKING and WS_DELIVERY_UPDATE_2. Both FMs update pick quantity (even it is different from delivery quantity - strange - online doesn't allow that), but not delivery quantity. Eventhough I pass delivery quantity in LFIMG field of vbpok structure.
I need it quite urgently, anyhelp? Thanks,
Regards,
Sundar.
Maybe you are looking for
-
ALV .....uregent plzz (some error message while executing)
*& Report ZAREPAS22 REPORT zarepas22 LINE-SIZE 250. TABLES : vbak,vbap,likp,lips,vbrk,vbrp,kna1,vbfa. DATA : ok_code LIKE sy-ucomm, g_container TYPE scrfname VALUE 'BCALV8_GRID_DEMO_0100_VASU', docking
-
Has anyone else lost all their phone numbers?
Just checked Contacts while trying to make a phone call and i don't see any of my phone numbers..I had probably 50+ in my contacts list. What gives? What do I do now?
-
Hi, While I was refresh the materialized view I found below error. SQL> exec dbms_mview.refresh(MV1','C'); BEGIN dbms_mview.refresh('MV1','C'); END; ERROR at line 1: ORA-12008: error in materialized view refresh path ORA-01652: unable to extend temp
-
Different versions of libCrun.so
I am using Studio 11. my executable just would not run with an older version of /usr/lib/sparcv9/libCrun.so on a machine and later I find out that a different libCrun.so is available with the Studio installation. Using LD_LIBRARY_PATH to pick up the
-
Cannot access portal thru IP address
Hi, I noticed that i cannot access my portal thru its IP. ie: http://<IP address>:50000/irj does not work but if i use the hostname to which it is mapped,it works.. what is the reason behind this? Thanks rocky