Send Scheduling Agreements as EDI to thirdparty

Hello,
We are trying to automate the process of sending the updated scheduling agreements if there are any differences in the validity range of the items. For this I need to trigger an EDI output from the program. I can directly call the routine RSNASTED routine after updating NAST entries but is there any standard way to trigger an EDI from the program ?
Thanks in advance for your help.
Regards,
Pavan.

Hi Jurgen,
I have changed the Scheduling Agreement via BAPI_PO_CHANGE and it created another version for the scheduling agreement. Now we want to trigger an output type for this changed agreement which in turn generates the IDOC which needs to be sent for third party system.
What do you mean by messages here ?

Similar Messages

Problems in sending Scheduling Agreement Change using ORDCHG

Hi All,
I am having problem while sending Scheduling Agreement change from a source system to a target system using ORDCHG in ALE,
Its going to ORDERS and creating a fresh new Sales Order instead of creating ORDCHG idoc's & creating a new order only for the chages.
Please provide some inputs on what Messge Types can support Scheduling Agreement change to Sales Order change.
Regards
Rajendra.

Hi Pavan,
Thanks for ur suggestion.
I have tried with DELINS message type, the IDoc is getting created but in the receiver side the status always remains 51 with message Vendor XXXXX not saved for the customer YYYYY.
Thanks
Rajendra

Automation of scheduling agreement through EDI

Hi,
My Client want to update the scheduling agreement automatically through EDI, so wants need to be configured in SD point of view.
looking for configuration details step by step
thanks.

hi all,
any one can give idea or information about this.
thanks.

Idoc Error Empty Schedule Agreement Purchasing Group Assnmt.

Dear Experts,
We have a job running, automatic sending Schedule Agreements' Line Items out through EDI
But some Schedule Agreements' field Purchasing Group is empty, Idocs created on these SAs are wrong
Idoc have wrong data filled in the Control Records, and segements are empy, status is set 26 in outbound process
because Idocs have wrong data, it is also very hard to trace
why ...
pls help ..

Using SU53 Immediately after Error will tell you what authorization is exactly missing. Send the screen shot to your BASIS team who normally incharge of giving authorization.
If you have authorization for SU22, check what authorization objects SAP check within that Tcode and check whether those object and appropriate authorization for them is maintained in any one role / profile assinged.
- Sunil Kolambkar

Delivery notes in scheduling agreements

Hello,
we send scheduling agreement (ME38) to our supplier. Now we create delivery notes with vl31n, which should reduce the open quantity of our schedules. Unfortunaly the delivery notes will not reduce the quantity and we send the supplier a wrong open, too high quantity. How can we solve this problem?
SPRO > Material Management > Purchasing > Confirmations > Set Up confirmation control
We set already the parameter for "Confirmation is Relevant to Materials Planning".
Regards
Andreas

Hi
You should use creation profile which has General data "Determine Backlog/Imm. Reqt" ticked for both JIT and Forecast . T.code is OMUP
Regards
Antony

Correct usage of Scheduling Agreements?

Hi Experts!
One of my groups is using scheduling agreements, however I do not think they are using it the way SAP had intended.
Example: They use Scheduling agreements, similar to a blanket order. However, the blanket order quantity is fluid and the order can remain open even when the initial quantity has been fulfilled. These Scheduling Agreements will contain many items, sometimes around 30-40 line items.
The staff basically conducts two activities for these customers: enter new scheduling agreements with updated validity dates and expedite releases with a less than two week time frame. These expedites are communicated by the customer via email.
The customers submit a 16 week forecast via EDI as well as a firm 2 week JIT. Most scheduling agreement activity occurs systematically, although there are daily expedites for each customer for a few parts.
Initially, when entering a scheduling agreement, the staff does not indicate the JIT schedule. However, they do enter into the Forecast delivery schedule, basically just to activate and allow communication from customer.
My concern is should scheduling agreements contain that many items?
Also, the staff makes many changes in the scheduling agreements and when it reaches the time when the period for the scheduling agreement, what ever material they did not get to ship, they ship it to the customer in one bulk. Are you suppose to do that with scheduling agreements?
In addition, sometimes the staff allocates some of the materials promised to the customer on the scheduling agreements to another customer, then just re-allocates it back at a later time...should this be done or is it bad business practice?
What are good business practices for usage of Scheduling Agreements? Any information will be greatly appreciated. Thank you for your time in advance!
WC

My concern is should scheduling agreements contain that many items?
Also, the staff makes many changes in the scheduling agreements and when it reaches the time when the period for the scheduling agreement, what ever material they did not get to ship, they ship it to the customer in one bulk. Are you suppose to do that with scheduling agreements?
you should not do that the reason is SA is use full for the JIT and promise to deliver things
In addition, sometimes the staff allocates some of the materials promised to the customer on the scheduling agreements to another customer, then just re-allocates it back at a later time...should this be done or is it bad business practice?
It's depent on the company bussiness policy - not rgiht process but if bussiness want to do then what else you can do?
What are good business practices for usage of Scheduling Agreements? Any information will be greatly appreciated. Thank you for your time in advance!
A customer scheduling agreement is an outline agreement with the customer containing delivery quantities and dates. These are then entered as schedule lines in a delivery schedule. You can either create schedule lines when you create the scheduling agreement or you can create them later.
You fulfill a scheduling agreement by creating the deliveries in the schedule as they become due. You process deliveries for a scheduling agreement in exactly the same way as you process a normal delivery. After you have carried out the delivery, the system updates the Delivered quantity field in the scheduling agreement item with the delivery quantity. The following graphic shows the document flow for scheduling agreements.
The same functions are at your disposal for processing scheduling agreements as there are for the sales order, including pricing and availability checks.
In addition to the standard scheduling agreements you can also manage scheduling agreements for the component supplier industry, with their special features that include:
Working with scheduling agreements with EDI output
Entering scheduling agreements in a forecast or just-in-time (JIT) delivery schedule
Using different types of cumulative quantities
Taking into account the automatic fiscal year change used by the component supplier
Managing engineering change statuses
Storing packing proposals
Creating correction deliveries for the scheduling agreement
Working with external service agents

Scheduling agreement from ECC 6.0 to SRM EBP 5.0

Hi experts
is there a way to send from ECC 6.0 to SRM EBP 5.0 all the kinds of scheduling agreements?
thanks
regards
andrea

Hi Andrea,
It is not possible to send Scheduling agreements from ECC to EBP.Same is the case with contracts.
You can only upload backend contracts to SRM. Using GOA you can create either a contract or a Scheduling agreement in R/3.
As informed by Usman, when you integrate R/3 (MM) with SUS it is possible to send S.As to vendors via SUS.
Hope this makes you more clear.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

EDI Message for Scheduling Agreement Schedule Lines

Hi Experts,
My client has the EDI set up for the SASL and is running fine.
Currently we have scheduled background program to trigger the IDOC and convert the IDOC into XML to send the information to the external system via interface after MRP run.Output type in the SASL will be triggered at header level (Without release documentation) whenever there is a new or change in the schedule line. Schedule line will be fixed automatically for every MRP run based on the Firm zone maintained in scheduling agreement.
Now the requirement is, Client wants to send the schedule lines regardless of New or change after MRP run sothat all the information will be sent to the suppliers. This requirement may be contradictory one but the client needs it.
1) For the New schedule line creation the output type will be triggered so no issues the program will take care
2) For the change schedule line also the output type will be triggered so No problem.
Requirement :
1) When there is no new & change in the schedule lines , how we can handle this???
2) Client wants to fix the schedule lines based on the planned delivery time and they do not want to maintain this PDT in the Firm zone field.??
Kindle explore and provide me the inputs. Appreciate your help.
Thanks /Karthik

Can you elaborate bit more on the issue.
see if you are not mentioning the PDT in the firm zone field. then it means the schedule lines can be changed and once they are changed the change idoc will get trigger.
however if there is no change in the schedule line and since its a old one there will not be any idoc generation for this.
seems as per your requirement you want to get the idoc generated for the old line as welll then u need to look for the anhancement badi/uer exit to map this.
need more insight of the issue to resolve it

EDI for scheduling agreement

Hello Experts,
We are having a scenario wherein our customer sends JIT and Forecast schedules which we update to already created scheduling agreements. The customer sends these details through EDI and we are using DELJIT.DELFOR01 to update the scheduling agreement.
Now for EDI, i guess SAP allows only 1 scheduling agreement at a time. However we are having scenario where we create a new scheduling agreement before the earlier gets complete (typically overalapping scenario) and customer can send the schedules with dates later than the current scheduling agreement.
The requirement is such extended schedule lines should be updated to new agreement while the rest should be updated to the current one.
If anyone faced such issue let me know.
Thanks in advance.
regards
rajeev

Hi Praveen,
we could always create a Z-function module. however thats lot of work and lot of customization. i am looking for a solution which would just be an enhancement to the existing funtionality (maybe some user-exit or enhancement or any configuration change).
regards
rajeev

EDI Message not Transmitted for Scheduling Agreement

Hi guys!
Does anybody know what should I check to see why the EDI message for a delivery line in the scheduling agreement has not been transmitted? Would really save me
Regards,
Ileana

Hi
First check the message whether it has been processed properly or not . goto ME39 , Check the message(Shift +F1)
if the message is in red, check the processing log,
If the message is in yellow , process the same using ME9E
If the message is in grren means the Idoc's are generated.
Now got Transaction WE05 & Check the IDoc's giving the Basic type - DELFOR02
Give from & to dates based on the rpocessing date of the message.
Here check the Idoc's are in Red or green . If in red check the Message in the Status.
Thanks & Regards
Kishore

Can anyone send me configuration guide of scheduling agreement

it is very urgent can any one send me configuration guide of scheduling agreement..
                                                 With Regards
                                               Prasanta Kumar Sahu

Dear Sahu,
          Go through this links these will help you in the Scheduling agreement processing and configuration.
http://help.sap.com/saphelp_47x200/helpdata/en/78/2085347860ea35e10000009b38f83b/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/33/4361299d7a11d194e200a0c9306794/content.htm
http://help.sap.com/saphelp_47x200/helpdata/en/70/a7853478616434e10000009b38f83b/frameset.htm
I hope it will help you
Regards,
Murali.

How to know if a schedulling agreement is created via EDI

Hello,
I would like to konw if a schedulling agreement has been created via edi. Is there any field or any transaction where is indicated so?
Thanks a lot!
Regards,
JMadariaga

Hi,
in your title bar "Display scheduling agreement xxxxx", you should have a "Services for Object" icon
If this is not present, you may have to add it to your profile in SU01
(Just set SD_SWU_ACTIVE to X)
If the icon is there, click it
now a small toolbar should appear
If the "display relationships" icon is not greyed out, click it
You should now see all the idocs associated with this scheduling agreement
Hopefully, the first one is the idoc which created the scheduling agreement.
Also, if you just wish to see the last idoc associated with the scheduling agreement
.After you click the Fore Dl Sch tab or the JIT DlSh tab
Click the Dlv Sch Hdr
Then Click the "Curr Idoc" and you will see your current idoc.
kind regards
Paul Quinn

EDI settings for Purchase scheduling agreement

Hello,
We are having one new requirement,
Purchase scheduling agreement created for foriegn or local vendor, the Schedule lines are created or release by MRP run.
After MRP run the schedule lines are going to create , then vendor can get the message though IDOC,
How can we customise the ALE and Idoc settings for above said scenario.

Hi Mahesh
After schedule lines are created for SA we have provision of schedule line release transfer to Vendor , please check whether output determination is feasible with medium as Idoc
Please check
Kishor

Scheduling Agreement

Hello Guru it is very very urgent plz give me answer what to do
This problem occurs in program Y_EX34_LVED4FZZ_001. The problem is that the current code assumes that VBEP-ZZSID will never be repeated by the customer, so all deliveries in the history can be checked when deciding whether or not to retain a schedule line. New information has confirmed that Nissan repeats their ZZSID numbers annually, which leads the current code to delete open schedule lines that had deliveries against them in prior years. Here are the recommended steps to correct this:
1.     After obtaining the VBEP data and before selecting from ZZDLVRANSID, find out when the relevant schedule lines delivery schedule was posted, using the following steps:
a.     Find the record in VBEH for VBEP-VBELN, VBEP-POSNR, and VBEP-ETENR that has the smallest nonzero value in the internal delivery schedule number field (VBEH-ABRLI). If none is found, take the record with ABRLI = 0000.
b.     Find the record in VBLB for VBELN and POSNR that matches ABRLI.
c.     Take fields VBLB-ERDAT and VBLB-ABRDT_ORG.
d.     If ABRDT_ORG is not 00/00/0000 or 12/31/9999, use it as the comparison date for this logic. Otherwise, use ERDAT.
2.     When selecting later from LIKP, also get the planned and actual Goods Issue dates (LIKP-WADAT and LIKP-WADAT_IST). If WADAT_IST is not 00/00/0000, use it for the comparison date for this logic. Otherwise, use WADAT.
3.     Before incrementing XLTOT_PGI or XLTOT_DEL, ensure that the delivery you are working with was shipped after the schedule line that youre working with was received (the VBLB date from step 1d is less than or equal to the shipment date from step 2). If it is, proceed with the calculations. If it isnt, dont add the quantities from this delivery into the totals.
Testing Strategy
·     In CTA, we will need to coordinate with the EDI team to find out if any customers exist that use replace logic for which data can be pushed in and tested.
·     In FTA, scheduling agreement 300027861 is an excellent example of this issue. We can get the EDI team to re-send data for that scheduling agreement (or for other scheduling agreements under the same customer), and process the IDOCs individually to test that:
o     Deliveries that were shipped prior to the open demands delivery schedule creation date are excluded from the assessment of whether or not to delete the schedule line.
Deliveries that were shipped after the delivery schedule came in are included in the assessement
regards
sapman

Only ABAPER will give the good result, but no body is taking risk
it is very urgent case
sapman

Scheduling agreement in SD, release number

Dear All,
I trying to implement an automatic process for one customer, getting in an EDI 862; transferring this in an IDOC message type DELINS of Basictype DELFOR02 and updating the scheduling agreement accordingly.
This is working fine, for simple cases, but this customer is sending different release numbers for the same product at one time, and also sending the release numbers multiple times.
e.g. today I am getting for product A a release number 111 with multiple schedule lines, and also a release numberr 112 for the same product with multiple schedule lines.
tomorrow I might get again an EDI 862 for this same product, containing revised information for release number 111 and 112.
This is in my understanding not matching the SAP logic, where it's clearly stated, that a new release number is replacing completely the old release number.
Does anybody has any idea how to implement such a process?
I already have studied all documentation, tried to implement it in different ways, but I am reaching every time only a 80 % solution.
Do we have in this community any experts on scheduling agreements on the SD side, which might be able to help me?
Thanks for any possible help.

check these
BAPI_CUSTSCHEDULAGREE_CONFDELV Customer Sched. Agreement: Confirmation of Delivery; Document Flow Upd
BAPI_SALES_DEL_SCHEDULE_CREATE BAPI for creation of releases in scheduling agreements

Send Scheduling Agreements as EDI to thirdparty

Similar Messages

Maybe you are looking for