Stop generating delivery IDOC output (outbound IDOC) if goods issued!

How to stop generating delivery IDOC output (outbound IDOC) if the delivery has been goods issued?! Any user exit or BADI for this?!
Thanks

We take a routine in output requirement! it's done!

Similar Messages

Converting Inbound idoc to Outbound idoc

Hii,,
How to convert inbound idoc to outbound idoc.
I have IDOC -> SOAP -> IDOC Scenario.
In case of error at SOAP side , it return idoc with 51 status.
Now i need to convert the Inbound idocs to Outbound Idocs and send it back to the Sender system...
How to do accomplish this??
Regards,
Siya

Hii,
By using we19 and by exchanging sender & receiver we can convert outbound idoc to inbound idoc.
Just want to confirm is it proper way??
Regards,
Siya

How to validate Expiry Stock at Outbound Delivery level instead of checking at Goods Issue?

Hello Everyone,
The client wants us to validate Expiry Stock at Outbound Delivery level instead of checking at Goods Issue?
What is the solution for this?
Regards,
Anwar

Hi Moazzam Sir,
I'm sorry for not explaining in detail. Actually, I posted the issue in a hurry. I apologize.
Actually, the client has materials which has expiry date. They use Batch Management. They maintain expiry data (90 Days) in Shelf Life Expiration Date. Their requirement is: User is creating sales order in VA01. Then, he creates Outbound Delivery (OBD), then PGI. They want system not to create OBD, if the material has expired. They want some error message to be thrown whenever user is trying to create OBD for expired stock.
Regards,
Anwar

Trying to change Inbound IDOC to Outbound IDOC for testing....

Hi Friends,
I am trying to do the following
1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
HELP!! Rewards

Hi Friend,
        The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
Use
You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an empty IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
Activities
·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the file type. The default file is the inbound file entered there.
·        You generate the IDoc using .
The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
·        Click on the white fields to change data in the segments.
In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
·        The additional procedure depends on whether you want to test inbound or outbound processing.
Test: Outbound Processing from MC
Use
Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
Prerequisites
You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
·        Customer or vendor records
·        Material records
·        Info records
·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as messages from the respective application.
The appropriate file ports and partner profiles must exist in the IDoc Interface.
Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to 1 (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
Activities
Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to Collect IDocs in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode Collect IDocs in live operation.
Activities
You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
You can decide whether the output mode is set to Start subsystem or Do not start subsystem in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Use
This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to File.
Prerequisites
A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are credited to the relevant IDoc in the form of status records in the SAP System.
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
Test: Inbound Processing: Modified Outbound File
Use
This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to File.
Prerequisites
You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type File must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
Standard inbound processing is then triggered;
·        Reading the modified file
·        Generating the IDoc(s) in the SAP System
·        Processing in the application
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
The recipient in this case is the SAP System. The port is used for identification purposes:
·        SAP (for example RSMITH
Test: Inbound Processing: Original Inbound File
Use
This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
Prerequisites
You require a correct inbound file. In this case, correct means that the:
·        Sender and recipient in the control record are correct
·        Direction in the control record is set to 2 (inbound)
·        Client in the control record and data records are correct or empty
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
The file is deleted after being read successfully!
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
·        Inbound port
·        Name and directory of the file
These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
Thanks

Delivery document is completed,but post goods issue.

dear :
devlivery docuemnt is set completed by Manually closing completed deliveries(programme:SHP_DELIVERY_COMPLETE),but it cann't post goods issue .so stock is exist .
how can i consume the stock ?
please help me analyse it .
best regards.

hello,
Check whether there are confirmed schedule lines in the sales order for which the delivery is made.
Also check if the storage location is there in the sales order
Regards
Mahesh

Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller: PIAFUSER
FM: IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server; and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

Link delivery to outbound Idoc

Dear Experts,
I am need to link a delivery to an outbound Idoc, I am using function module BINARY_RELATION_CREATE to create the link and I can see the link has been created in the delivery but it showing as Incoming Idoc instead of Outgoing.
I am using relationship type IDC1 in the FM and have tried using others and have failed miserably, could anybody help me??
code
   wa_rolea-objkey = doc_number.
   wa_rolea-objtype = 'IDOC'.
   wa_rolea-logsys = wa_logsys.      <-- From FM D_OBJECT_TYPE_DETERMINE using document type (VBTYP)
   wa_roleb-objkey = delivery_number.
   wa_roleb-objtype = wa_objtype.     <-- From FM OWN_LOGICAL_SYSTEM_GET
   wa_roleb-logsys = wa_logsys.      <-- From FM D_OBJECT_TYPE_DETERMINE using document type (VBTYP)
   call function 'BINARY_RELATION_CREATE'
     exporting
       obj_rolea            = wa_rolea
       obj_roleb            = wa_roleb
       relationtype         = 'IDC1'

Hi,
try to use value "LIKP" for variable wa_roleb-objtype.
BUS2015 = Inbound delivery
LIKP = Outobound delivery
Regards

How to re-run output determination after goods issue through idoc

Hello,
i've got a question about output determination. We are currently in a process to automate picking, packing and goods issue through a 3rd party software. The software creates DELVRY03-Idocs including picking, packing and goods issue-information. Picking, packing and goods issue work just find and after submitting the idoc, the delivery is updated as needed.
The problem arises when it comes to printing the shipping document on the printer belonging to the picking station that just processed the delivery. To determine the correct printer, the external software includes the picking station number inside the idoc. A user exit in idoc_input_delivery puts the number (3 digits) into likp-traid. The customizing for using this field inside output determination is complete and seems to be working.
The problem is: as the number of the picking station is not known before goods issue, the LD00 message must not be generated before goods issue. I used the appropriate condition insinde the message scheme, the message is not generated until goods issue is complete. After processing the DELVRY03-Idoc, the message should be found and generated, but it isn't. When i take a look at the delivery after submitting the idoc, goods issue is complete, picking and packing is done - and no sign of an header message of type LD00. First i thought about a misconfiguration inside my customizing for output determination, but when i access the delivery via vl02n (change delivery), output determination seems to be processed again and without making any changes or actions, LD00 is generated and waiting for processing. After saving the delivery, LD00 is processed and the shipping document is printed exactly where it should be.
So, as my customizing seems to work and everything else around idoc processing doesn't make any problems either, i conclude that, after processing the idoc, R/3 just needs a little kick to re-run the output determination, find the now fitting condition for LD00, find the appropriate entry in the condition table and print the document.
I already tried report rsnast00, but this one just seems to run already created messages.
Any ideas how to automate this little "kick in the butt"?
Thanks in advance!

I'm working on a similar issue with ws_delivery_update. I'm not using the IDOC as you are, but I'm using the function in a program of mine to PGI the delivery, but the output isn't being added to the delivery. I've tried to run the function twice as you suggested, but that doesn't seem to work. Do you have any suggestions or ideas on things to try?
Thanks,
Eric

Generate DELVRY Idoc when Post goods issue is done in SAP

I need to generate an Idoc when post goods issue is done in SAP (outbound to SAP) .I understood that I can do this using the message control .The message type DESADV with the process code DELV will support this.
But I didnt understand how to trigger the Idoc.In the current scenario our Company is doing the post goods issue in SAP for the in three different ways.
1.Manually doing the post goods issue through the transaction VL02N
2. an Inbound Interface (using Idoc) which will do Post goods Issue in SAP
3.Another Interface using BAPI, which will, do post goods issue in SAP
I have to run my outbound interface when the post goods issue is done by all the above three ways. Can any one help me out in this?

You have to configure the output first .
You can use output type LAVA ( avaialble in Std SAP ) .
( Tcode is NACE , Select Application V2 -> Outputtypes ).
( Create condition records suitable to generate an output)
Next is ALE.
Setup a distribution Model ( for DESADV ) and all other setup for ALE i.e. Distribute Dist. Model / Generate Partner Profile .
In the Partner profile in WE20 select your partner system. Double CLick on Outbound Message DESADV ( this wd be there after you generate partner profile , if not add it here in outbound ) . On this screen goto tab MESSAGE CONTROL .
Application - V2
Message Type - LAVA
Process Code - DELV.
Now you are ready to go. The moment a PGI is done in any form an output LAVA would be proposed and processed using process code DELV.
Cheers.

Configuring shipping point as Trigger point for posting outbound idoc

Hello All,
I have a requirement that on saving an Outbound Delivery(VL02N), an Outbound Idoc should be posted...but the condtion for posting the idoc should be its shipping point. I am not sure how to configure shipping point as the trigger point for the idoc.
Please suggest.
Thanks for your co-operation.
Regards
Anand

Hi Anand,
1. Go to transaction: NACE & select application V2 and click on output types.
2. change display <->Change mode.
3. select LAVA and press F6 (to copy Standard output type LAVA to ZLAV).
4. Give ur Z name for the new custom output type.
5. change access sequence from 0005 to 0012(shipping point).
6. Press ENTER and click copy all.
7. Now goto trasaction VV21, give the created output type name. ENTER
8. Maintain entries, shipping point, customer#, Medium as '6' ...etc
Now try VL01N with the given shipping point and check the output ZLAV has been triggered or not?
Let's see, if we miss any configs still!
Keep this as reference:
http://www.erpgenie.com/sapedi/messagecontrol.htm
Reddy

Send inbound IDOC as outbound(copy)

Hi,
We need to send the same inbound IDOC as outbound IDOC to the customer(they want to get a copy of it) How can we do this? We are getting inbound sales order IDOC's and the customer wants the copy of the same IDOC, not order acknowledgement. Is it possible?
Any inputs are greatly appreciated.
Sarita

I can think of following:
You create your own Process code, Function Module to update your data using Inbound IDOC and at the end generate outbound IDOC using same data and then distribute using MASTER_IDOC_DISTRIBUTE.

Mapping Inbound-Outbound IDocs

Hy everybody,
Is there a table in the receiving system where inbound IDocs numbers are linked to outbound IDocs numbers from the sending system ?
Regards,
Christian Baldari

Hi,
there is no link from inbound idoc to outbound idoc.
We will only come to know by looking document flow.
Sales order - Docuemnt flow
Delivery - Docuemtn flow.
You will come to know all the things by looking docuemnt flow.
ramesh

How to reverse goods issue for delivery note by using IDoc

Hi all,
I would like to reverse goods issue and picking request for delivery note by using inbound IDoc.
I used message type SHPCON and IDoc type DEVLRY03 for posting goods issue in inbound processing and it's work but I couldn't find solution for posting reverse goods issue.
Pls let me know which IDoc type or any ways for posting goods issue reversal and cancelling picking request.
Thanks for your time.
Su R.

Hello,
          For this requirements we can actually follow two Approaches that I can think of. Here they are.
Approach 1
         Little Complex Approach. What we can do is to make use of the Same Function Module (Posting Program) IDOC_INPUT_DELVRY to do the Delivery Updates (Except reversing the Goods Issue). During this, we can make use of one of the Customer Functions available in the Enhancement V55K0001 and satisfy our Requirement.
Approach 2
        We can actually code a Custom Posting Program (Function Module) in which the first part will take care of updating the Delivery & if the PGI is done, then we can make use of the Function Module BAPI_GOODSMVT_CANCEL to reverse the PGI.
        I think the later Approach is much easier rather than going for the Standard Function Module (Posting Program), Exits and find a place where we have to find another Enhancement Spot / Enhancement where we can call the above FM to Cancel the Goods Movement.
Hope these inputs were helpful.
Thanks and Regards,
Venkat Phani Prasad Konduri

SLSRPT Inbound or Outbound idoc ?

is SLSRPT inbound idoc or outbound idoc and what is the Process code used ?
Thanks
Praveen chindam.

Hi Praveen,
Welcome to sdn.
This function allows you to receive and process the following types of partner transmissions in CRM:
· Resale Report u2013 (ANSI X12; EDI 867, Message Type SLSRPT)
it is an inbound idoc.
see this link
http://repository.edifice.org/migs/slsrpt3/compare.htm
thanks
trinadh

Help on IDOC -POST GOODS ISSUE

Hi Folks,
I have requirement with me, but I dont know where to start could you please help me regarding that..
Here is the scenario....
Requirement Specification:
XYZ Company Mexico operations uses third party systems Foursite) for their inventory process.
The communication between Foursite and SAP is thru EDI/IDOC.
In the case of goods customer return to Mexico warehouse, using the following steps the process will be mapped in to SAP.
Customer calls the account specialist.
Account specialist creates a ZO order in SAP and conveys a RA to customer.
Account specialist creates a delivery. The delivery information conveyed to Mexico warehouse thru Inbound receipt IDOC.
Customer physically returns the goods to Mexico warehouse.
Mexico warehouse receive the goods with reference to delivery number in Inbound receipt IDOC.
Once the goods are received, Mexico warehouse send a conformation (Receipt confirmation IDOC) to SAP, which triggers PGI and credit memo.
Functional Specifications:
Create POST GOODS ISSUE in SAP for the material and quantity for the delivery mentioned in Receipt conformation EDI.
Receipt confirmation from Foursite
Data fields received in the EDI
Delivery number:LIKP-VBELN
Material number::LIPS-MATNR
Quantity:LIPS-LFIMG
Unit LIPS-MEINS
Plant :DMEX
Status :RS
Possible IDOC: SDPICK
Trigger:
This IDOC should trigger a Post good issue, for the possible values.
Transaction: Post good issue.
Please give ur input /suggestion , What steps I should take to get it complete .
Thanks in Advance..
Bye and have a good one .

Somnath,
If I understand the right, it is like a integration using EDI formats. Do you have a middleware in place to do the mapping transformation? If yes, the message in EDI format will be recieved by the middleware and will be transformed into IDOC format.
Then you do the normal settings for an IDOC to be recieved into a SAP system (Partner Profiles, Inbound Messages etc).
Is this what you were looking for?
Regards,
Ravi
Note : Please reward the posts that help you.

Stop generating delivery IDOC output (outbound IDOC) if goods issued!

Similar Messages

Maybe you are looking for