Triggering Outbound idoc in VL10UC

Dear sdn members,
Its related to outbound Idoc generation online in SCM. The requirements is that whenever a sales order created in CRM system ,automatically outbound delivery will be created in ECC. For that I can check in VL03N transaction in ECC.
But that outbound delivery will be unchecked in ECC. In VL10UC we can combine and check the delivery and a new delivery document will be created and old document will be deleted and automatically one outbound idoc should be generated in ECC for the new delivery document.
Can we handle this using message control or any other way to handle this since a online interface.
Message Type-DESADV
Basic type-DELVRY05
Process Code-DELV
Function Module-IDOC_OUTPUT_DELVRY
Reward points for useful Answers
Regards,
Krushna

Its solved.

Similar Messages

Triggering outbound idoc from the transaction VL01N

Hi,
I have requirement where in which i need to create outbound idoc of sales and delivery data as soon as VL01n transaction is saved,Pls let me know how we can achived this , the Idoc needs to be triggered immediatly after saving VL01n transaction.
Thanks
Ravi

>
Sujatha Reddy wrote:
> Hi Ravi,
>
> Goto t-code NACE, select Shipping and press push button 'Output Types', now you will get the output type for delivery and you can configure you own output meduim in this screen.
> select the meduim & assign the require parameters.
>
> and goto VL01N and create a delivery and now you can goto extrats-> delivery out put-> header, here you can assign the output type that has been confugured perviously.
>
> -hope this helps
You could of instead told them to search the forum like I did. Instead you chose to give him the answer, even though it is not the full answer. After they have done what you ask, what result would you expect form the output record on the delivery. I will tell you, it will not process, why, because you have not mentioned anything about partner profiles and the output control.
But I hope you get the points for you reponse and you sleep well.

Message type :FIDCC2/ IDOCFIDCCP02 - Triggering outbound IDOC

I have to send the FI accounting document of certain customer groups to the third party system .
Can anyone pls let me know how to trigger the outbound IDOC for the message type FIDCC2 after the FI document is created.
I have configured BD64 but can not find which program to trigger to generate the outbound IDOC with the FI data.
Thanks,
Prashanth

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

Triggering Outbound IDoc, when doing the Goods Receipt in MIGO

Hi All,
I want to create an idoc(outbound), when i do the Goods Receipt(MIGO, Movement type 101).
1. Can we trigger the IDoc through output Determination.(I have configured for VL01n -outbound delivery & VL31n-inbound Delivey.It works... But is there any same way for MIGO)
2. Is there any other way to trigger the IDoc when document saves in MIGO.
Please Help On this.
I m eagerly awaiting for Solution.

Hi,
Go through the following link:
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=waytotriggertheIDocwhendocumentsavesin+MIGO&cat=sdn_all
It might help you.
Thanks
Rajesh Kumar

Outbound IDOC not getting triggered while new master data is created

Hi Experts,
I am trying to trigger an outbound idoc for Cost Center master data when ever cost center is being created or cost center is being changed. (Usinf COSMAS)
I have successfully made use of change pointers and now able to trigger the idoc when ever Cost Center is getting changed. But while creating new Cost center, IDOC is not getting triggered.
I used the function module MASTERIDOC_CREATE_SMD_COSMAS for triggering the idoc.
Could one of you please let me what would have gone wrong? Since IDOC is getting triggered while changing the master data but not getting triggered while creating new master data.
Thanks in Advance,
Vinoth

Hello,
when you activate BD21 for a message type, it creates a entry in the SAP tables. that these Cost Centers have been sent already and any susequent changes to this will trigger a IDoc.
As for BD16, scheduling it wont help as, you need to specify the selection criteria, and i do not see how you will be able to dynamically get the selection criteria.
Try BD95, and BD59 to create a change pointer for a field, so when ever this fields is modified (new/updated) an idoc will be triggered.
regards,
Abhishek

How to find the Program that triggered the outbound idoc

Hi,
I need to find the program that triggers a particular Outbound IDoc.
I have the IDoc number/segment/message type.
We need to Debug the Outbound IDoc but we do not know from where the IDoc got triggered.
Is there a way we can find which program triggered it?
Thanks!

Hi Suresh,
Go to tcode WE20, select ur partner profile type, which configured in output type for EDI documents.
On right side, double click on the Message type in outbound parameters.
go to message control Tab, double click on process code variable to see FM triggers for the IDOC.
same as for Inbound also.
Regards
Syed A

Duplicate Outbound IDocs getting Triggered at the same time.

Hi Folks,
I have created custom outbound idoc and done all the configurations required like WE20, WE30, WE31, WE81, WE82, WE 41, WE57 etc.
Also I have written my code to populate segments and then call MASTER_IDOC_DISTRIBUTE in the custom function module which is assigned to the process code and also done the configurations like we57 etc. for the same.
Now when I trigger my output type from VL74 transaction, I noticed two entries in we02 resulting in two IDocs generated for 1 HU.
The difference in two IDocs is the first IDoc getting generated in error with status 29. While the second one as success with status 03.
The data records containing segments have same values for both the IDocs number.
Whether the configuration is a issue here or problem in code of custom fm?
Please help.

Hi Anil,
Appreciate your quick response.
In my custom FM I have populated an internal table it_master_idoc_data with two records of two segments, containing segment name in SEGNAM filed and segment data in SDATA field.
Please let me know whether the data in this internal table of structure EDIDD sufficient for passing to MASTER_IDOC_DISTRIBUTE FM? Or do I need to populate any other field of EDIDD.
Also I am exporting a structure master_idoc_control containing values in this 5 fields.
MESTYP = Z message type, Z IDOCTP, partner and details in RCVPOR, RCVPRN, RCVPRT fields.
I am not populating the internal table communication_idoc_control while calling FM MASTER_IDOC_DISTRIBUTE from my custom function module.
After executing MASTER_IDOC_DISTRIBUTE FM, when the control comes back to my custom FM there is one record in communication_idoc_control internal table with IDoc number in DOCNUM field with status 29(error). Now when we check in WE02 there are two IDocs generated after this transaction's execution.
The first one in error which FM MASTER_IDOC_DISTRIBUTE returns and second one in success with status 03.
Please help....
Thanks,
Pravesh

Triggering of DESADV Outbound IDOC

Hi Gurus,
can anyone assist me in telling the process involved and steps to trigger DESADV type Outbound IDOC of type 856
thanks in advance;
Sunil

Go to NACE and select V2 and click output type from menu.
Give following value.
Condition component Value
Access sequence 0005 (sales organization/customer)
Condition 0 (no condition)
"Exclusive" select
Output type LAVA (shipping notification outbound)
Procedure V10000 (shipping output)
Application V2 (shipping)
Processing subroutine Program RSNASTED,
form routine EDI-PROCESSING
General data Select Condition access and Multiple sending of output, otherwise
leave the fields blank
Time e.g . 4 (immediately, IDocs are generated immediately after
posting)
Transmission medium 6
Partner function WE
Language DE (German)
You must maintain following values for outbound partner profile.
Message type : Desadv
Partner type : Ku
Partner function : WE
Port : Subsystem
Outbput mode: Collect idoc
Basic type : Delvry01
Packet size: 1
Application: V2
Output type : LAVA
Process code: DELV.
You can post the delivery by selecting Logistics ??Sales and Distribution ??Shipping, Delivery
-->Create (transaction VL01). Output control is used to find the condition record and the shipping
notification is sent to the customer via EDI (IDoc Interface). The shipping time in the condition
record determines when the corresponding outbound IDoc is generated
On the Create Condition Records (Outg. ship notifica.): Fast Entry screen:
-->Enter customer number in Customer, SAP Ship-to # .
-->Enter WE in PartF.
-->Enter 6 in Medium.
-->Enter 4 in Time.
-->Enter EN in Language.
-->Choose Save.
Thanks,
Narayanan

Triggering ZTransaction outbound idoc

Hi,
For one Ztransaction development, i have to trigger an outbound idoc. hw to do this & pls share the steps & code for the same.
Regards,
Balaji

Hi wg,
thanks for the quick reply.
the link provided by U is on target for my query. By the program, i can create this idoc as per the steps given.
But as Seshagiri's suggestion, while updation in zdb tables, frm that ztransaction, the code to generate idoc when it is saved is the similar code given in link or any difference is there?
thanks again...
Regards,
Balaji

Outbound IDOC process - Using standard or Custom Program

Hi all,
i'm having some doubts regarding IDOC's outbound processing.
I'm trying to understand 2 scenarios:
1- Trigger Standard Outbound IDOC without writting any Z program ou IDOC FM.
It's possible to trigger a outbound idoc for exemple, whenever a sales order is created. To do this is, i suposed i don't need to write any code at all, correct?
What i need to do is create a logical system (SALE), define Transmission protocol (WE20, in here i associate the partner, and the outbound message type? After this point is the idoc automatic triggered?
If not, what is the correct procedure?
2 Trigger Ountbound IDOC using Z program.
Whats is diferent from the point 1 to this situation?
Best regards,
Pedro

Kali,
1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
3.Again ans is same as in point 1.

Change Business Partner in CRM to trigger OutBound IDOC in R/3 system

Hi Team,
I am stuck on a requirement, We have a scenario were the Business Partner is created in CRM system
which creates a BDOC and is passed to R/3 system through an Inbound IDOC which triggers the Outbound IDOC to PI system. So far good.
The scenario we are getting stuck is when a Business partner is changed in CRM an IDOC triggered in R/3 system but this being a change the Change pointers are not called hence the IDOC which is supposed to be triggered for the PI system is not getting triggered.
Can you please tell me what steps should I take to trigger this Outbound IDOC from R/3 system?
I did some anlyasis and found a table which COM_BUPA_CALL_FU which contains a set of function module which is triggered in the sequence. Is this the solution or if you have any different do let me know.
Thanks,
Imran

Hi,
Did you add the entry for your new custom 'Z' long text inPITX Tcode in R3 side. Every long texts in CRM should be linked to R3 long text here. If there is no entry please add one and try changing the text in CRM.
Hope this helps,
Karuna.

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

Attaching Error Status to Outbound IDOC. ?

Hello Experts,
We have a scenario in SAP PI / XI were upon creation of a Sales Order , Purchase Order or Material Master Flow to Non-SAP System through SAP PI/XI , the IDOC shouldn't flow to SAP PI following a validation on Material Group.
The IDOC is triggered through Output Type , there is a custom Z function module which create outbound communication IDOC. This output type is attached to a Process Code ZSO, ZMPO defined for respective scenarios defined above.
Currently i am attaching the the status = 07 to control data structure & the IDOC is getting created but is having error.
Is this the right practice to follow for attaching error message Outbound IDOC.
Awaiting for your response.
Best Regards
Priyesh Shah

It depends on the business requirement.
in a previous project, if there was any error during the validation of the data within the iDoc before it is created and sent, i would trigger an error and send the error to the person who created the data with the error for them to correct. they would then correct the error within the document and save and the iDoc would be triggered and sent correctly.

OUTBOUND IDOC DEBUGGING

I have Output type defined for the application V3
i.e meant for Billing.and the output type is custom development with name ZD00 for invoice-Bill to.
This output type is defined for edi processing.
Now the problem is when invoice is created and this
outputtype is selected the quantity field in idoc and invoice differs.just get double in idoc.but if the same output is fired again data in idoc gets corrected.now i want to debug the idoc outbound processing.what i did i run the transaction we41 and find the process code and find the function module that is running in the background for collection of data of invoice and
filling the idoc.but but but the problem is i put break point in the function module to check the value at run time but this is not triggered . iam confused tell me how to debug the outbound idoc.
Help me out i will be waiting for the response.

Hi,
You can use the Update Debugging. If you know the prognam name/function module of your source code, upon saving your document, a new screen will pop up if the Update Debugging mode is on. From this, you can then hit F8 to stop on your break-point.
Let me know if you need further help.
Thanks,
Eric

Outbound idoc resend

Hi all . I have come up with a requriement. The scenario is as the following
    once we raise a sales order and save it ,an outbound IDOC gets triggered and send to the customer via EDI. after some time customer asks for one more copy and there is a need to change the values of some of the fields and resend to the customer. This can be done in two ways
1.Go to va02 make the requried changes and issue the output
2. change the idoc which is already processed and resend it
    our client wants to go for the second option.
Can anyone help me out
1.' Where we can change and resend an already processed outbound idoc '?
2.if we make any changes in an outbound idoc at idoc processing level will the changes reflect in the order?
3. Can we restrict the user to change certain fields only?
Any inputs given by you people will help me a lot.
Thanks in advance
Srini

Hi srini,
As i Understand the senario, Their might be some changes to the document required by the customer. This also needs to reflect in the changes in Order.
It will be complex way to update both the IDOC and order, if you are changing in the IDOC and resending it. It would be more wise to go ahead with the first option making changes in through VA02 and then sending it accross . And most of the companies do not hold the IDOCs for too long & hence it would be wise to make changes in VA02 and send the IDOC once more. This can be done by minor code change based on the edit checks business wants to perform.
Well if you still want to go ahead with the second option here are answer to the questions.
.' Where we can change and resend an already processed outbound idoc '?
First the IDOC status needs to be changed from program RC1_IDOC_SEt_status
then you need to reporces it throught program RSEout00
2.if we make any changes in an outbound idoc at idoc processing level will the changes reflect in the order?
The changes will not reflect in the order unless you have a code written in SAPLxved.
3. It is not possible to restirct the change to certian fields only.
Reward points if this helps
Thanks,
Kamal
Message was edited by:
        Kamalakar vp

Triggering Outbound idoc in VL10UC

Similar Messages

Maybe you are looking for