Several deliveries are created through IDOC message type DESADV.

Hi Gurus,
Do you happen to know why in IDOC, message type DESADV, FM BORES_IDOC_INPUT_DESADV1, several inbound deliveries are created? What could have been tha reason for the split? One strange thing is, we tried to create an inbound delivery manually using the same material or data in idoc but only one delivery were created. No split occurred.
I tried to investigate and i found out that Idoc uses FM GN_DELIVERY_CREATE while manual creation uses GN_DELIVERY_CREATE_FOR_DIALOG. Do they have difference?
I hope someone can help me on this.
Thanks in advance!

Hi
Answer is pure assumption.
LIKP-ZUKRL is the field used for delivery split, pls check whether you are passing any value for the same
Regards
Madhan D

Similar Messages

How link customize IDOC message type with FM ?

Hi,
I have created new IDOC message type ZCOST and FM ZMASTERIDOC_CREATE_COST. (Outbound).
Please advise how link the message type and FM ? so everytime i am executing BD21 with message type ZCOST the program always calling FM ZMASTERIDOC_CREATE_COST to generate the IDOC.
Thank You and Best Regards
Fernand

HI,
You need to link Mssage type, IDOC type and the FM (also extension idoc type if exits) in TCODE: WE57 --> go to change mode
--> then new entries --> even you need to gove the direction inbound/outbound.
Also you need to create a outbound custom process code in WE41. and link the FM to the process code.
This process code shold be assigned to the partner profile in we20 in outbound parameters -> so you FM will be picked up qutomatically.
regards,
Nazeer
Edited by: N a z e e r on Jul 14, 2010 3:14 PM

IDOC message type or bapi to create CRM Product hierarchy

hi all,
I tried to tranfer the Product hierarchy to CRM using LSMW, it could not transftered by batch input and I could not find any IDOC message type or bapi to create Product hierarchy. it seemed that I could not using LSMW?
i also found that many BAPIs in CRM were not related with ALE message.so we can not use LSMW using IDOC or BAPI to transfer data? i will very appreciate anyone who can tell me to solve such problem, especially tranfer data to CRM. thanks so much!

hi Ramgopal,
u can check the bapi-BUS1112 for cost center, and from the methods what ever u want u can take based upon requirement
if u find it useful plz mark the points.
check the IDOC method with message type COSMAS and basic type COSMAS1
it should workout now
Regards,
Naveen
Message was edited by: NAVEENKUMAR GUDURI

IDoc Message Type to create Inbound Delivery + Confirm + GR

Hi Experts,
I need IDoc message type which can create Inbound Delivery / Confirm / Create GR with Inbound Delivery as reference and i dont want to use DELVRY05
because I need to create Inbound Delivery / PICK / Confirm but not with Transfer Order Creation means Unnecessarily we dont want to create Transfer Orders. We need to exclude Transfer Orders and create GR.
Please do the needful.

Dear Kishore,
It's possible via writing code in enhancement spots of transaction code VL31N, MIGO_GR/MB01.
R,
Amala

IDOC message type LOIPLO not triggering

Hi Friends
Our client want to send firmed planned orders to External system through outbound IDOC LOIPLO
So we are using MF50 to firm the planned orders.
The idoc message type LOIPLO is not triggering.
How to trigger IDOC message type LOIPLO . What are the settings we have to do.
Regards,
Srihari.M

dear friend,
Message Type : LOIPLO
Basic Type : LOIPLO01
You need not create any custom IDOC type as we are having a standard IDOC type available within SAP, but you need to write a custom function module to read the data from the IDOC segments and then call the below BAPI to post the Planned Order.
Check the input parameters of BAPI and gothrough the documentation of the Basic Type in WE60 transactions, whether all the necessary input parameters of the BAPI are covered in the standard IDOC type, if not then we need to customize the standard basic type to meet the requirements.
Bapi which needs to be used is BAPI_PLANNEDORDER_CREATE
good luck!

Attribute extension generation to IDOC message type CRMXIF_IBASE_SAVE_M

Various attributes have been defined and assigned to a set type using tcode COMM_ATTRSET. The set type includes an entry in field CDB Table CDBD_ATTRVAL. The Create API Append has been checked when including in a transport which generated the API append structure for the set type. The set type has been assigned to a Category via tcode COMM_HIERARCHY.
We are planning to use IDOC message type CRMXIF_IBASE_SAVE_M for the legacy data migration. How do we include the new attributes?

You have to use TCode BDFG to generate a new Message Type . This will create a new Message type and a new Idoc type and will include the new Atributes.
we have used to create a new Message type for our new fields in ACTIVITY_H ( extended through EEWB )
Make sure , you refer to some OSS Note , which will tell you the steps to do so , As for first time user of BDFG its very tricky.

Idoc/message type related to su01 tcode fields?

hi experts,
when i create a user in su01,an idoc should get triggered.
are there any standard idoc / message type having fields related to this.
thanks,
charu
Edited by: charudevrani on Jan 11, 2012 7:38 AM

Hi Charu,
You can use one of following IDoc types, depending on the action you want to perform on the user master record:
USERCHANGE     Change user
USERCLONE     Create User with Template in Another System
USERCREATE     BAPI to Create a User
Regards,
Marcin

IDOC Message Type FIDCCP02 - Error RW029

Hi All,
We are trying to post a FB01 using a IDOC message type - FIDCC2 and struck at error message -
Accounting transaction not permitted for posting in FI/CO
Message no. RW029
When i try to post directly using the exact data in the IDOC, through FB01, there is no problem.
Debug showed that the error is in the following -
Include LRWCLF01
check business process
SELECT SINGLE * FROM t022 INTO ld_t022
WHERE activity = t_acchd-glvor.
IF sy-subrc IS INITIAL.
IF LD_T022-VORGTYP = 0 OR <---------
IF ld_t022-satztyp <> 0.
MESSAGE e029 WITH t_acchd-glvor.
ENDIF.
ELSE.
MESSAGE e029 WITH t_acchd-glvor.
ENDIF.
If this is not the right message type to use, can you suggest any other message type? FB01 we are trying to post is a simple GL posting, no tax, no withholding, etc. IDOC is just a 2 line posting.
Any help/advice is highly appreciated.
Many Thanks,
Shashi

Hi Shashi ,
This table is for Business Process t022 based on activity .
Check your customise settings .
There is no problem with message type .
Please reward if useful

IDoc Message Type different in sending to receiver system

Hi,
I am sending DESADV (message type) IDoc to other SAP system. But problem is in other system Message Type DESADV is available in a different name ie DESADV1.
No of segments and their name are same in both the system are same..
In that case if i am sending DESADV from sending system whether receiver system can get IDoc?
Note: In sending system i could not able create message type DESADV1
Sa_R.

Hii..
Looking like Strange scenario...
Normally we must have the Same message type in both Sender and Receiver systems.
Bcoz whenever the IDOC is Received in the Receiving system it will process based on the Message type. So the Same message type must exist in the Sender as well as Receiver.
I can think of a Solution: Just try..
In the Sender system Create a Reduced message type (Tcode BD53) Of the Message type DESADV. Select all the Segments and Fields
In the Receiver system also Create a Reduced message type with the Same name as Sender system (Tcode BD53) Of the Message type DESADV1. Select all the Segments and Fields.
Then use this Reduced message type since it exists in both the Systems.
Reward if Helpful.

IDOC message type reduction

I have a PLM system that will be receiving Material Master Data from multiple R/3 systems.
I will need to create a reduced message type for MATMAS.
Need confirmation of steps:
1. I create a reduced message type ZMATMAS in the PLM system (BD53)
2. Activate change pointers for ZMATMAS in PLM (BD53)
3. Generate transport request for ZMATMAS in PLM (BD63)
4. Import reduced message type into all the R/3 systems (STMS)
5. Verify distribution models in R/3 systems (BD64)
6. Send material from R/3 systems to PLM system (BD10) using reduced message type
The question I have about these steps is whether I should create a reduced msg type in all the R/3 systems (multiple times) or is it ok to do it one in PLM as described above?
Please let me know if steps are correct?

Hi Raynald LaGuerre ,
1.To create a new message type, follow these next few steps:
     Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
     Choose Create logical message type by double clicking on it
     Click on change icon to enter change mode
     Click on New entries to add a new type
     Enter the required message type
2.WE82--LINKING OF MSSAGE TYPE TO IDOC TYPE(DISPLAY).
Rgds
Sree M

Contract creation in Backend with Idoc message type BLAORD

Hello,
We are creating Backend contracts from the Bidding engine functionality. We only want to create backend contracts and did the necesary configuration.
We activated BADI: BBP_DETERMINE_LOGSYS
Method CONTRACT_LOGSYS_DETERMINE.
We did not yet implement BADI:
BBP_CTR_BE_CREATE in SRM 5.0
In SAP R/3 Backend system (Version 46C) we see SAP is trying to create a contract via Idoc message Type: BLAORD.
In the trx BD87 in the backend we get status 51 :
Mesage number: 00 055
"Make an entry in all required fields"
In the segments of the Idoc however we do not see which field is missing!
How can we best analise this problem. Or maybe anyone can give us a a hint what is missing.
Thanks for any reply.
Aart

Hello RRK,
In ref. to your mentioning to change the backend configuration from WKK to MKK might not be as easy to do for organizations. As those configurations effect the overall creation of purchasing document types in R/3.
The Key issue is why the "Target Value" in the Header of the SRM GOA does not get transferred to the R/3 contract. That's why the issue is still there.
Were you guys able to figure out why that was missing? In the BLAORD IDoc the Target Value seems to not get transferred from SRM - its 0.00 if the IDoc is reviewed in WE19. This seems to be the problem.
Just wanted to know if you see the same issue in ur system.
Thanks.
Sunny.

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

IDOC message type for "Site" in SAP Retail module?

Hi All,
We have the need to transfer master data (through master data change pointers) of Retail Sites within the SAP Retail module (transaction: WB01, WB02). Does anyone know if there's an IDOC message/type already associated with this? Thanks in advance for your help!
Cheers,
Matt

Hi,
please read SAP notes 892103 and 551035.
The correct IDOC type should be FIDCC1 / FIDCC2.
Best regards,
Andreas

How to get the segment detials of IDoc message type.

Dear Friends,
I want to write function module , which takes the IDOC message type as an input and returns all the segment fields in response.
Basically I want to get the XML schema of a IDOC message type and need to expose these details toa 3rd party application to use.
Dear experts ,Please do give me some ideas how to achieve this .
like tables from where i can get these details or u feel any other goos way of doing the same.
thx,
jeevan

Hello experts,
Please participate .........
To redefine my objective I will say:--
I am trying to do some thing very similar that is there in XI .
You might have seen the way IDOCs are shown while mapping an idoc structure.
Its like you select a message type and u get all the list of Idoc Structure shown .
I am really relying on you people.
thx ,
jeevan

Equivalent Idoc message type for EDIFACT BANSTA

Hi Experts,
I am trying to find out the equivalent IDOC message type for EDIFACT BANSTA. The purpose of the message is to show the item level statuses for a particular payment batch. There are lot of references about FINSTA01, however, this is for account level status response.
If anybody know the equivalent idoc message type for EDIFACT BANSTA, kindly let me know.
Thanks in advance.
Regards,
Ravi

Thanks raja shekar. I posted this thread in ABAP development forum.

Several deliveries are created through IDOC message type DESADV.

Similar Messages

Maybe you are looking for