Additional Materials Added in Delivery created via. IDOC.

Hi,
We have about 1000 incoming idocs which creates and PGI the delivery automatically. when verified deliveries we saw that customer entered was wrong and hence reversed all PGI (VL09) and Deleted all deliveries (VKM4).
We then used Functional Module RC1_IDOC_SET_STATUS and changed the status of idoc back to 51.
1. We process idoc manually in BD87 to create 4 - 5 deliveries they were created and PGI as required.
2. Now when we gave all idoc numbers (about 980) and then reprocessed in BD87. we saw a strange behaviour in the system some unwanted material were added to the deliveries. Checked were not the same as in idoc eg. If idoc has 3 materials delivery will either have 3(required) + 2 (added unwanted) = 5 materials or will create a duplicate line items. There were no changes made in idocs.
Request your suggestions.
Thanks and Regards
Ashish

Hi,
Yes we have deleted the deliveries created and then reprocessed the idoc from the original system and we could see that deliveries are now being created successfully without any issues.
We think this is buffereing issue. and the reason is that we mass updated the idocs and the created all via BD87.

Similar Messages

Delivery date getting calculated wrongly in delivery created via VL10D

Hi Gurus,
We have a strange issue, where in delivery date is getting calculated wrongly for replenishment delivery created via VL10D.
When we are creating via VL10D , delivery date is getting the additional 30 days from MaxDlvCrteDate . With initial investigation i see that VL10D has delivery creation profile 0101 for which no of days maintained in max delv creation date is 30 .
I assume that the delivery date is getting the additional days from delivery creation profile felid no of max delv creation date .
I have created the delivery on 24.03.2011, as per the route no of TL time is 9 days , So Ideally the delivery date should be 04.04.2011 , however system has calculated it as 23.04.2011
Delivery no No of days in MaxDlvCrteDate Delivery date
213443158 30 23.04.2011
If I create the delivery for the same PO using t-code VL10B, then delivery date is calculating correctly.
Not sure why system behavior is strange.
Please help me with your inputs to resolve the issue..
Thanks in advance

Please request one Abaper to solve this problem.
You cannot due nothing as the problem is in Code.
Regards
William

No Centry in CDHDR when Cost Center is created via Idoc

Hi All,
Whenever a cost center is created via an Idoc the corresponding entry is not maintained in CDHDR table.
Whereas if I use Tcode ks01 to create Cost Center (ie via screen) then there is an entry to CDHDR table.
I tried debugging the FM IDOC_INPUT_COSTCENTER .
Here in PERFORM write_ale_cp_via_cd tables LT_CSKS,
there is a call to CALL FUNCTION 'IDOC_CD_WRITE_CHECK,
here ld_active is always initial.
If I set this as X while debugging then I do have my entry in CDHDR table.
Can anyone let me know the significance of this ld_active and why is it not set to X initially.
As it is important for me to have entry in CDHDR because I need to trigger an event as a cost center is added.
Kindly advice.
Regards,
Sweta

Sweta,
The same problem has lingered with me for awhile now. Finally, I have a solution.
The controlling area needs to be configured for master data distribution. Take a look at the view V_TKA01_ALE to confirm that the controlling area(s) that you are working with have a logical system(TKA01-LOGSYSTEM) and distribution method(TKA01-ALEMT) set up. These fields are checked in the IDOC_CD_WRITE_CHECK function module. If they are blank, no change documents are created.
Hope this helps.
Brad

Return order with reference to the billing document created via IDOC.

Dear Colleagues,
I’m struggling to understand and confirm whether standard functionality of ORDERS05 idoc allows creating a return order with reference to existing billing document?
I have tried using standard segment E1EDK02 and E1EDP02 with qualifiers 009,010,011,087 but unfortunately idol is not creating a return order with reference and ignoring this segment.
Have any one came across similar problem? If yes then will be grateful for sharing his experience.
Best regards,
AL

Dear Friend
Welcome to SDN
Return order is itself a challenge to SAP standard settings
There are some scenarios
1. Return order qty should not be increasesd say Billed qty of material X is 20 units
While returning Material X should be a maximum of 20 units
If made 21 it should throw error T code OVAH message class V4 message no 299 convert from warning to error thro customization
2.Return order should be created only once referencing billing doc
To control that T code SE91 message class V1 message no 499 convert from warning to error thro ABAP help
3 Your issue is same like case 1 but the material X is entered as second line item in the return order with some qty
This case system is not throwing even a warning
Yes correct
This is to be handled with userexit
Discuss the same with ABAPer
Check these threads on return issues which is of different scenario than of yours
Forum post in ERP - Sales and Distribution (SD) General: Order Qty.
Order Qty.
Forum post in ERP - Sales and Distribution (SD) General: Return order
Return order
Regards
Raja

Multiple Shipping notifications (Inb.Dlv) created via message type DESADV

Hello All,
I'm working on implementing the below SAP Standard process for my client. Version is SAP 4.7. The below process has to be implemented for different legal entities working on Same SAP environment.
PO -> SO (Created via IDoc) -> Outbound Delivery -> Inbound Delivery (Shipping Notification) -> Invoice -> Invoice reciept.
Most of the process are working, but facing few challenges while creating a shipping notification via message type DESADV and Basic type DESADV01 genereated out of Output type LAVA from Outbound delivery.
I'm using 2 IDoc types to create Shipping notification via Outbound delivery and defined as below
Outbound Process: Message type DESADV and Basic type DESADV01 with Process code SD05 for Customer (KU)
Inbound Process: Message type DESADV and Process code DESA for Logical system (LS)
I'm facing the following issues with respect to above process
01) We need to update Batch Details like batch number, Date of Production, SLED/BBD in Shipping notification (Inb. Dlv) as Batches Instead of vendor batch
02) When Outbound delivery has multiple line items, it is creating Multiple Shipping notifications (Shipping notifications for each line item). PO has
As per the the threads posted here, I understand that for 01) We need to modify the Outbound IDoc FM "IDOC_OUTPUT_DESADV01" & Inbound IDoc FM "IDOC_INPUT_DESADV". But any idea, which Enhancements i have to use to fill the data?
Also on point 02) i think, it should be a SAP standard to create a single Shipping notifications for all line items in the outbound delivery instead of each for line item. But in case if it is not a standard process, can any one tell me which user exits / enhancements to use to achieve the desired functionality.
Appreicate your early response
Thanks in advance
Regards,
Pradeep

Hi,
Why have you pasted Deepak Kumar's program into this forum?
Regards,
Nick

Adding Purchase Delivery Note with SerialNumbers via DI Server

I try to add Purchase Delivery Notes via DI Server. It already works for items that do not need serial or batch numbers. But if I try to add a PDN with an item that needs such numbers, I'm getting an error that the line of the item cannot be added without these numbers.
Then I tried to add SerialNumbers to my request, but I am still getting the same error.
The xml template for the SerialNumbers part looks like this:
<SerialNumbers>
<row>
<SystemSerialNumber />
<ManufacturerSerialNumber />
<InternalSerialNumber />
<BatchID />
<ExpiryDate />
<ManufactureDate />
<ReceptionDate />
<WarrantyStart />
<WarrantyEnd />
<Location />
<Notes />
<BaseLineNumber />
</row>
</SerialNumbers>
Can someone explain me, how to use it?
What are the mandatory fields?
What is <BaseLineNumber>? Is it the line number of the item in the purchase delivery note?
Do I have to include <SystemSerialNumber> or will this number be generated automatically by SBO?

Hi Nico,
you should use the SDK Help Center to determine the mandatory fields...
When creating an incoming document (Purchase Delivery Note) with serial numbers using the DI API I assign the InternalSerialNumber property only and this works.
The only Mandatory field when creating an outgoing document is SystemSerialNumber which is the unique key for a serial number...
As a side note, I am still experiencing some strange behaviour trying to use the DI API to create documents using serial numbers. I am in contact with SAP regarding this but am getting very slow responses...
Daniel

Packing a delivery via idoc

Hello,
I am trying to understand how to pack a delivery via idoc. I am using message type SHPCON and idoc type DELVRY03. I see a segment E1EDL37, but field EXIDV is mandatory, how does external system know the value for EXIDV, which SAP generates dynamically.
Appreciate your help.
-Naga

Hi Naga,
I am facing similar type of problem (DESADV - DELVRY05). I am trying to create and Inbound Delivery and Pack immediately via Idoc. I had populated the fields for Handling Unit in E1EDL37, 39, 44 segments.
Delivery was created successfully, but Packing info is not stored in VEKP/VEPO tables.
Pls advice.
Thanks in advance,
Murali.

How to create Inbound Delivery using SHPMNT03 Idoc details...

Hi,
I need to create <b><b>Inbound delivery</b> using idoc SHPMNT03</b> details. I am getting all the data required to create Inbound delivery is from this idoc. for that I need to create a custom function module.
I tried with FM IDOC_INPUT_DESADV1. But it is for only if you use DELVRY03.
I haven't (yet) found a way to create automatically an inbound delivery when you post the goods issue from the outbound delivery.
Does anyone experienced the use of inbound deliveries with STO and what are your recommendation?
Thanks a lot,
Ranjith.

Hi there,
Please have a look at the following link.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/dc/6b828943d711d1893e0000e8323c4f/frameset.htm
Hope this helps,
Kind Regards,
Matthew

How create an invoice from delivery using an idoc

Hi expert,
I'll like recive an help to know how implement the following solution: we would create an invoice from delivery sent into the idoc structure.
In detail the process that we would implement is:
To use an output type for outbound delivery and to assign a program to it in order to create an idoc when the output type is processed; when the idoc is created the program has to call the transaction VF01 to create the invoice from the idoc.
Which type of idoc do we have to use?
How the VF01 call transaction should be excuted?
Many thanks in advance
Regards
Roberta

Check with following standard basic IDoc types:
INVOIC01- Invoice/Billing document
INVOIC02 - Invoice/Billing document
INV_ID01 - Invoice
SISINV01- SIS - billing document
And refer following link for understanding: [iDoc|http://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=HOME&title=StepbyStepprocedureforcreationof+IDOC&decorator=printable]
I hope this can assist you.
Thanks & Regards
JP

Idoc at status 51, however outbound delivery created

Hi Gurus,
We have peculiar issue , where in outbound delivery is getting created through IDoc. The inbound idoc has status 51 however delivery got created. Any idea how is it possible?.
Thanks in advance.

Dear Math,
Have you got the solution for the above. If you get can you tell me please because even i got the same error message while processing the IDOC
status 51 after status 53. Outbound delivery is updated but not the sales order.
can you please help me

IDOC, created via BAPI-CALL?

Hey experts,
I´m looking for a way to identifiy, if an IDOC has been created via a asynch. BAPI-Call or if it is a usuall IDOC.
Can anyone help me?
Thx a lot!
Oliver

Oliver,
He is not talking about any Idoc. He is talking about the acknowledgement. Check this help on this:
http://help.sap.com/saphelp_nw04/helpdata/en/44/932e8896b610bbe10000000a422035/frameset.htm
---Satish

Auto Packing in outbound delivery via IDOC

Hello All,
I got a requirement for Auto-packing in outbound delivery via IDOC process.
Can anybody through some light on the above requirement in finding Message type, process code and so on...
your every suggestion or hint will help me to fulfill the requirement.
Thanks in advance.
Best Regards
Suresh.

Hi,
Auto Packing message type: SDPACK
Process code: SDPA
Basic type: SDPAID01
Regards
Suresh.

Creating a IDOC during outbound Delivery posting

The requirement is to create a IDOC J3ADES01 when an Outbound delivery is created.
Can you kindly suggest ways of doing this?
I planned to search for BADI or user-exit and create a IDOC within it.
But not sure.

By the way, what message type and basic type can be used for these FM?
I also found a lot of opinion from here, some say DELVRY03. some say DELVRY04, some say DELVRY05.
Is it no problem with using which basic type here as long as it fits the data that u want in the IDOC?
Please advice.
Thanks.
Best Regards,
JL

Confirm Outbound Delivery with HU number via iDoc

Hello SAPman,
I am trying to confirm a outbound delivery thanks to iDoc,
the context is the following :
Storage location is managed with HU but there is no SAP WM.
The goal is to get an iDoc from a external WMS with the HU which had been picked.
I tryed with iDoc based on message WHSORD / SDPACK / DESADV
but each time, the iDoc integration stop because SAP find the HU filled in the iDoc in the storage location, and don't want to use it.
mesg HUSELECT 005
My need is to affect the HU filled in the iDoc to the outbound delivery and post the good issue.
Did you ever work with an eternal WMS with such a need ?
Best Regards,
Jérémy

Hi,
it is quiote some time ago that I have worked with that, but have you considered to establish a LEAN WM in the SLOC which is controlled by the external WMS system?`
In this case you will have Transfer Orders and you can work with WMTORD/WMTOCO
Additionally you can leave the lean WM as it is without a mass of config and it should be possible to work properly with HU's.
Best regards
Uwe

Creating HR objects via IDoc HRMD_A05

Hi to all
I want to create HR objects via IDoc HRMD_A05 and want the objects numbered using INTERNAL number range.
The IDoc documentation says to pass an exclamation mark '!' to OBJID to make the system generate new number. However, the field is numeric and can not contain '!'.
Has anybody tried this way before and achieved to create objects numbered internally?
Thanks

Hi
I have told the issue to the SAP OSS and their feedback was:
"As explained in note 741165:
'There is no provision to carry out an internal number assignment using
ALE in the target system. Therefore, the numbers must be assigned when
the IDOCs are created in the source system.'
The documentation in the Interface Repository is wrong.
Regards
*--Serdar

Additional Materials Added in Delivery created via. IDOC.

Similar Messages

Maybe you are looking for