Trigger TPSDLS01 IDoc to external TPS when outbound delivery is deleted

Hi,
We are currently trying to find a solution how to trigger a TPSDLS01 IDoc to external TPS when the outbound delivery is deleted.
In the following SAP article: Logical Communication Processes Between the SAP System and the T - Supply Chain Planning Interfaces (LO-SCI) - SAP Libra… it is said that "...If a delivery is deleted in the SAP system, this deletion command is transferred automatically to all transportation planning systems...". and we're trying to understand how it actually should be configured?
Any advice would be much appreciated.
Thanks!

Hi,
I know this is quite old now....but, did you ever find an answer to this problem?
SR

Similar Messages

Changed delivery does not trigger TPSDLS01 IDoc to external TPS

We have a R/3 Release 4.6C server, which is configured to send delivery IDoc (TPSDLS01) to external transportatoin planning system (TPS) via ALE/RFC.
When a new delivery is created, we can invoke VT61 to transmit TPSDLS01 to notify TPS. When a delivery is deleted or deallocated, R/3 immediately transmits the TPSDLS01 IDoc to notify TPS. These all work just fine, but we have a problem:
When a delivery that has already been transmitted to TPS but got modified after the first transmission, we need to be able to transmit it again to notify TPS of such change. However, R/3 refuses to transmit it again. When invoking VT61, nothing get transmitted and the log would say the delivery <delivery id> already transmitted to planning system <TPS ID>.
I am new to this, but it seems to be a simple configuration issue. I am suspecting the problem may come from the output parameters of our partner profiles. On the "Message Control" page for outbound message type TPSDLS, we have nothing defined.
On page 8 of the R/3 Transportation Planning Interface Document (https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9519a090-0201-0010-189d-a9d947b30a8e), there is a paragraph:
Deliveries that are changed in R/3 (transaction VL02) after they have already been reported to the transportation planning system are automatically retransferred after the changes are posted (provided they are relevant to transportation). This functionality is activated by the link to message control. When a change is made, the whole document is retransferred (not only the changed data is transferred).
Could anyone explain what this "activated by the link to message control" means (in terms of steps and exact field values)? Or if you think the problem is from elsewhere, please let me know.
Many thanks.

Hi,
I know this is quite old now....but, did you ever find an answer to this problem?
SR

Trigger IDoc when outbound documents are deleted

Hi Experts,
I am working on a scenario where in when delivery document is deleted then we need to have a IDoc to be triggered and sent to the receiver.
I understand that when we create/change delivery, there is a way to trigger IDoc (i.e., through message control). But when we delete a delivery, I am not sure, we have standard mechanism to trigger an IDoc. Can we have a standard way of making this happen?
Thanks & Regards,
Suraj Kumar

Hi,
In the NACE transaction, Click on the APPLICATION V2 and create a new OUTPUT type with Z as prefix
In the Processing Routine Tab in the control data enter the MEDIUM as 6 which is the EDI and maintain the PROGRAM & SMARTFORM as developed by the ABAPer
Now maintain the CONDITION RECORDS with the MEDIUM 6 and the LS as Partner function
Now with the Help of your ABAPer, define the PARTNER PROFILES in WE20 and the Message types .
This will trigger the OUTBOUND idoc to the other system.
Please check these settings and revert back if you need more details
regars,
santosh

Req: Save Valuation Type in PO when Outbounde delivery is created and Saved

Hi Gurus,
I have a requirement.
1) PO is created
2) Outbound Delivery is created with ref to PO and saved . The VALUATION TYPE entered in outbound delivery needs to be updated in the PO.
please guide me in which user exit in Outbound Delivery can I update a PO valuation type.
and also how can i change it whether through a BAPI or Direct table change.
Avi.

Hi,
I have resolved this issue, I'm posting here so that it could be useful to someone.
To trigger output from Inbound delivery, I have setup a new output and also developed a process code XXXX. A new FM is developed for this process code.
In the new/ customized FM, I have called the standard FM 'IDOC_OUTPUT_ORDERS' which is used to pull PO data for ME10 process code.
It is know that we have to pass PO number as object-key to the FM to pull the PO data but when a output is triggered from inbound delivery object-key will be a delivery number.
Write a simple select statement which will get the PO number from EKES and set this as object key and pass it to FM 'IDOC_OUTPUT_ORDERS' .
Thus, you can generate an outbound IDOC which has PO data when triggered from E1 application (Inbound Delivery).
Thanks,
Santo
Edited by: santo29 on Jan 13, 2011 9:44 PM

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 HRMD_A06 Missing Infotype When Outbound

Hi All,
I'm using message type HRMD_A and basic type A06 for my HR outbound IDOC interface.
I did not put any filter for the distribution model, however, when I execute the outbound, it only outbound the IT 2 and IT50 for me. Other infotypes are missing (eg IT 1, 8, 9 etc).
Can you tell me what did I setup wrong? Hope someone can help me because it's urgent.
Many thanks in advance.

Hi,
Hard to say... Are you using PFAL for distribution? Have you check the application log (SLG1 - Object HRALE)?
Have you tried to debug RHALEINI (PFAL)? Are you using an evaluation path to get your population? What transfer mode are you using? (insert? update?) Did it actually works once or you just never make it works?
Kr,
Manu.

Automated error email notification when outbound IDOC fails

Hi,
The requirement is that whenever the outbound IDOC of message type PAYEXT, basic type PEXR2002, fails, then email has to be trigerred to a group id.
I had suggested to write a report program that runs as a job. If the IDOC goes to error status then mail will be sent from this report. Client prefers it to be done through workflow.
There is a standard process code for outbound IDOC failure handling EDIO (we40). standard task 7989 has been assigned to this process code. I dont want to modify this standard task as I am not sure of impact.
Terminating event for this task is 'ERRORPROCESSCOMPLETD'.
I have developed the workflow that has trigerring event 'ERRORPROCESSCOMPLETD' and bound with the IDOC number. This will send mail to the group id with the IDOC details
Now issue is that, I am not sure if standard process EDIO will be trigerred automatically, or should we configure anywhere. Since this is standard outbound IDOC, I am not able to add the process code in partner profile.
Please give your inputs or any other alternate solution to send mail through workflow when outbound IDOC fails.
Thanks in advance.

Hi,
I guess in your outbound partner profile for PAYEXT. you need to add process code EDIO in message control TAb. WHich will cause to trigger the workflow which will send the notification.

How to trigger FIDCCP02 idoc for outbound vendor invoices?

Hi
1. How can i trigger the idoc FIDCCP02 for outbound processing? I am trying to use this idoc to send the vendor invoice data to another system.
2. How do i send existing data from sap to another system thru idocs?
pls give me the steps.
Regards
Sujai

Hi Sujai,
First you have to fill the your data into a table which is like the structure of EDIDD.Here you have to fill the all segmetns in the sequence which defined in the idoc type only other wise you will get error 26.
Then pass the control record data in the structure like EDIDC here you have to fill the sender,receiver,partner profile,idoc type message type like stuff.
Then pass these table and structure to the function module MASTER_IDOC_DISTRIBUTE.
Then idoc will created by above funciton module.
If you want pass data in xml format then you have to create xml port in we21 and pass this port name in the EDIDC structure.
Thanks,
radha.

Trigger an Idoc when a sale order is been opened in VA02 & saved

Hi Experts
     I have a requirement to trigger an Idoc when a sale order is been opened in VA02 transaction and saved.
Now that I have attained the same through Message Control Settings and Nace out put type settings with Multiple Issuing.
Here in the Idoc will be triggered when the user makes any changes in the order based on the NAST table entry.
Now my requirement is that the Idoc has to be processed even if there is no changes made to the document when the user opens the sale order and clicks save.
This is the process been carried out to re-process the Idoc.
Now that the Idoc is triggered using the path ---> menu - extras -output - header- edit & save.
Now that the user need to process the Idoc by just opening the order in VA02 and click save.
How can this be attained ? is there any configuration for it ?
Or is it possible to handle the same in any of the user exit ?
the problem is the user exit save gets triggered only when there is any change in the document else it throws a msg " No changes made"

Hi Niraj
   Thanks for your Response.
Now that the output control works fine when there is any change made to the document.
Now that i need to configure such a way that the output control triggers even if there is no change to the document and save   button is clicked.
Can U please elaborate how do i make settings in VOFM-> Output Control ?
Thanks
Sathish

How to trigger an idoc when 'For Approval' button is clicked in IMA11 trans

Hi Everyone,
I have requirement that an IDoc should be triggered when the button 'For Approval ' is clicked. I have created the required IDOc but I couldn't find the way to trigger it. Can anyone help in this regard.
Thanks in advance
sandhya

You can't get the "OK Pressed" directly, but you can check the error output. An error code 43 is generated when a user hits cancel in the dialog box.
If you're using a vi from the File I/O pallet (like "Write to SGL File"), they unfortunately don't have the error cluster wired as an output. They do have an output of the selected path. This is set to "Not A Path" if the user selects Cancel. Test the output path - if it is equal to the "Not A Path" constant, then the user hit cancel.
Tim

Automatically Trigger a Idoc when a sale order Document is changed

Hi Experts,
Currently Idoc is pushed manually through sale order change transaction " VA02 " menu path
" extras - > output - > header - > edit "
I have done the nace settings for output types & condition records . Now that the Idoc gets triggered automatically
when a document is created in VA01 transaction. Is there any other settings required such that the IDoc can be sent automatically once the document is changed and saved through VA02 transaction also.
Or do I need to process the IDoc through user exit of VA02. Kindly advice how to proceed with it.
sathish
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on Mar 17, 2011 12:48 PM

In Partner profile(WE20), you can make one mor entry similar to existing record with check box enable, under Message control tab.means maintain the below details, Application, message type, process code and enable the change check box.
After making entry in WE20, you can change sales order and save the application.It may work.

File to IDOC, with External Definition to hold multiple IDocs

Hello Experts,
I am configuring a sample File to IDOC scenario. Here are the steps I am following, can you please guide me what I am missing here.
I am having a flat file with 10 records to be transferred to my ECC system through IDOC adapter to create 10 different IDocs.
1. I am picking up my flat file using a 3rd party Business System with File Content Conversion
2. I uploaded CREMAS Idoc and exported as XSD file and modified Occurences paramter to unbounded and uploaded back as an External file definition into IR
3. I defined an SAP WEBAS ABAP type Business System with LS (representing my ECC system) and configured with IDOC Rcvr channel.
4. In the IDOC recvr Channel, I specified RFC destination pointing to my ECC system & Port, Release...etc
5. On the ECC side, I configurated a PARTNER PROFILE with the above mentioned LS(used in step 3) and added an Inbound Idoc paramter CREMAS with process code CRE1. Selected the option Trigger Immediately.
Testing:
1. When I checked my CC monitoring in RWB, my file on the sourced is getting picked up successfull with respect to the specified polling intervals.
2. I don;t see any messages in my SXMB_MONI. I verified SXMB_ADM configuration it looks fine to me
3. I used TCode:WE02 on ECC side, nothing is there
4. I used Tcode SM58 on ECC side, nothign is there
I have no idea what is happening after successfully picking up the file on the source side.
Is there a way to trace where exactly the error is or what is wrong with my scenario?
Just an observation, We don;t need to specifiy any LS on the Sender Business Sytem(3rd party in my case) which picks up my file on the source side. Rather I am specifiying LS on the Target Business Sytem(type WEBAS ABAP in my case) to send my IDOC to ECC system. I am using the same LS to define PP on ECC system.
Edited by: Chris Rock on Oct 21, 2008 5:03 PM

Aamir,
I tried full cache refresh, also cleared SLD Cache for both IR & ID. No luck.
I think either some thing wrong in connection parameters, but atleast if I see some error in Moni or RWB, it helps, but in my situation, nothing is showing up there.
Connections:
I specified PORT & RFC Dest in IDOC RCVR Adapter along with WEBAS Release version. These PORT & RFCs are created in XI using SM59 & IDX1 and both passed the connection test.
On the ECC side, I created a PP with inbound Idoc CREMAS and process code as CRE1. This PP uses the LS that was used in RCVR BS specified in XI side.
I also loaded Idoc meta data into XI with Tcode: IDX2
Please help me, any body. I will sincerely award the points.

Trigger an IDOC

Hi Guys,
I am doing the IDOC to File scenario I want to know how to test my scenario and how to trigger an IDOC.
Thanks,
RameshBabu

1.Log in to sender system, go to transaction WE19 (test tool to generate IDoc), generate IDoc of the required message type.
2.Give Receiver and Sender System Info(Port, Partner No, Port Type and Message Type) and click on Continue
3.put some entry into the IDoc before you send
4.click on Standard outbound processing button the following screen will appear: Click on continue again continue. In the last window Idoc sent to Sap system or external program information should appear else you may have to check Receiver and Sender System Info(Port, Partner No, Port Type and Message Type) for valid entry
5.Execute Transaction WE05; enter correct date/time frame and logical message type. Hopefully the Idoc Status should be 3 (successful), if not check the status code and correct the error and reprocess the message. You can use transaction code SM58 with enter correct date/time frame and execute. Here if it is successful then nothing should be available in the list else it will show the relevant Status / Message. WE02 transaction can be used to get the error info.
6.Log in to Xi system and execute transaction SXMB_MONI and check for the XML messages. Use your source and destination system to filter messages
7.Check the destination directory, it should have file with the name specified. Check the file; it should have data for all segments

Sales Order - Outbound Delivery IDoc scenario.

Hi Friends,
I have the below urgent requirement. I would be gratful, if someone suggest possible options.
Scenario: This is related to Sales order to Billing scenario.
We are creating Sales orders by using ORDERS05 Idoc. After the Real goods despatch happens at legacy system, we will be getting despatch feed (IDoc) for outbound delivery trigger. Here if all sales Order items are complete, the system is creating Outbound delivery by using this IDoc and then PGI will follow. This is Ideal scenario.
Practically what happening is, our sales orders are created with few incomplete items (Ex: Net price missing) because they are created via ORDERS05 Idoc.( Manually, we can't create sales order with incomplete items, unless we force the system to do so). When the Out bound delivery IDoc triggered, it will pick up only completed items and creates partial delivery and becomes 53 status. Now the sales order is left out with open and incomplete items.
Now our aim is how to make this outbound delivery IDoc fail, if this is not able to create delivery for all items?? (I mean, if the sales order items are incomplete, the delivery Idoc must fail. So later, if sales order becomes complete, this Idoc can be reprocessed again) How can we make this scenario possible??
Expecting your thoughts and inputs.
Regards,
Kaleeswaran

HI,
I suggest you to think of similar solution as below.
1.As your issue is at order (few items are incomplete with Pricing issue or some other issue), at sales order level while saving each sales order write the code in user exit_save_document_prepare to check if any items exists as incomplete. if yes then populate a delivery block in the sales document header.(you can use a new delivery block to distinguish the reason for the block)
2. While creating delivery for the order through Idoc since the incomplete orders have a delivery block at the sales document header level SAP wont create delivery for the entire Order.
3.Handling this delivery block at sales order header: when ever a sales order is popluated with this new delivery block triggere a workflow which will shoot a mail to your End user team or customer representative team. they will correct the issue in the order and remove the delivery block. if you dont want to go with a workflow then you need to incorporate a process to remove the delivery block in the sales order
Thanks,
Srini

Create ORDRSP Idoc on creation, change or deletion of outbound delivery

We have ORDRSP Idocs being created when a sales order is created or modified. Now our customer would like an ORDRSP Idoc sent to them when the outbound delivery is created for the sales order. The reason that the customer would like an additional ORDRSP sent is because the time between the entry of the sales order and the creation of the outbound delivery may be a few weeks or more and the actual delivery may not be able to satisfy the quantity ordered. The customer is not set up to allow partial deliveries.
The customer uses the ORDRSP to feed into their billing system and would like updated quantities at delivery time. They do not want an ASN record.
Does anyone have any ideas or suggestions on how to trigger the ORDRSP Idoc when the delivery is created, modified or deleted? We are on SAP release ECC 6.0
Thanks for any help,
Russell

Vinit and Abhishek,
Thanks for your replies and information. Sorry I was not clear in my question. The ORDRSP Idoc is already being created when the order is created or changed. ORDRSP works fine. The partner profile is set up, NACE is already configured for ORDRSP, change pointer is working properly, output determination is configured and working, the ORDRSP Idoc is being created.
What I would additionally like to do is trigger the creation of an ORDRSP Idoc when the delivery for the order is created or modified. I suspect this will require using a user exit in the delivery program to trigger the ORDRSP Idoc and not standard SAP configuration. This is what I would like help on (trigger the creation of an ORDRSP Idoc when the delivery for the order is created or modified).
Also this site is a small shop. I am the ABAP programmer, the functional consultant and the EDI consultant for all SAP modules. There is no one else on the team here other than one person that does transports and security for SAP.
Thanks,
Russell

Trigger TPSDLS01 IDoc to external TPS when outbound delivery is deleted

Similar Messages

Maybe you are looking for