Movement Type 351 against scheduling agreement for future dates

Dear Gurus,
For stock transfer orders(Inter Plant Transfers), if the schedules in receiving plants are available only in future(say after 15 days), the sending plant is able to make 351 against such scheduling agreements today itself.
Is there any way to control 351 movements against these scheduling agreements.
Please reply.
Points would be awarded.
Regards
Shankar

Hi,
we are taking multiple GR against Scheduling Agreement hence for Parking Invoice we are using "Delivery Note" as reference.
but when we maintain delivery note system is not showing multiple GRs against Scheduling Agreement
Invoice Parking is not done against these Invoice
Please advce

Similar Messages

In MIGO against Scheduling agreement for Consignment error

Dear SAP Gurus,
I m getting abn error in MIGO for SA
"Maintain pricing conditions for the material for the excise invoice date"
vinod

>
GSMY Volvo wrote:
> Hello,
>
> We want to receive material against delivery schedules of Scheduling agreement.
>
> Our setting are.
> No MRP
> Delivery schedules are created manually.
> No confirmatin control.
>
> Issue is, delivery schedules are future date but i want to make MIGO today without changing the delivery schedules in ME38.
> Is it standard SAP setting that we will not be able to receive the material for future dates ? or is there some setting in background ?
>
> Sundar
Its standard SAP setting that migo cannot be done with delivery in future dates. To do migo, change the delivery schedule to today's date and then do the GR against the SA.

Automatic Creation of MIGO for stock transfer order with movement type 351

I have used the BAPI - BAPI_GOODSMVT_CREATE_OIL to create the material document number. But the test ended with error "Goods movement not possible with mvmt type 351".
Is there any ways to eliminate the above error....
Friends need your help

351 Goods issue for a stock transport order (without SD)
The quantity is transferred from unrestricted-use stock in the issuing plant to stock in transit in the receiving plant.
Movement type 351 is only used if the goods issue is posted without an SD delivery. A goods issue for a stock transport order with SD delivery is posted using movement type 641 or 643.
The transfer posting is also possible for materials valuated separately.
The goods issue for a stock transport order takes place using movement type 101.
Possible special stock indicators: E, Q
For special stock indicators E and Q and for purchase orders assigned to an account, ensure that the quantity is not posted to the stock in transit in the receiving plant.

BAPI for Goods Issue (MIGO) movement type 351 with reference to PO

Hi,
Is there an BAPI for Goods issue in MIGO with reference to PO movement type 351, i tried using "BAPI_GOODSMVT_CREATE", but there is no PO field in this, is there any other BAPI's available for the same?
Thanks in Advance,
Santosh

for goods mvt type , the available is that itself . for 351 mvt type Po number is not required .
if its a must , create a Z bapi with additional field for PO and make it as reference .

Post Goods Issue for movement type 351

Hi experts,
I need to perform a post goods issue for the movement type 351.
which bapi we need to use? is it going to be "BAPI_GOODSMVT_CREATE" or something else.
What are the information that we require other than movement type for performing post goods isue?
Any pointers on this will be highly appreciated.
Regards,
Sajith

Hi ,
Thanks man.. Then where should I do that.
Idoc is PORDCR102. Message type is PORDCR1.
My requirement is to create a STO first in the user exit EXIT_SAPL2012_001 and then to perform a Post goods issue in the user exit EXIT_SAPL2012_003.
Can u please explain it.
Regards,
Sajith

Perform Post Goods Receipt Against Scheduling Agreement

Dear all,
I've weird problem here. This is concering GR against Scheduling Agreement. I've a "LPA" type Scheduling Agreement and all the delivery schedule maintained and schedule line released successfully in ME38.
When I do GR via MIGO by entering the Scheduling Agreement #, a prompt was given with no items selected. Note: My schedule line delivery date = GR posting date.
What I did was, inside MIGO I go to Settings | Default Values and check on "Propose All Items". Finally, the affected line item appears but with "blank" quantity. So, I key in the actual quantity per the released schedule line and complete the GR posting successfully.
Question 1: Why do I need to perform the MIGO propose all items setting? Normal PGR against PO doesn't require this.
Question 2: Is this a standard SAP behavior or I'm doing PGR - scheduling agreement process the wrong way?
Appreciate any expert clarification.
Thanks in advance.
Steven

Hi Jurgen,
I've read Notes 493404 and I'm facing Question 10
10. Question:
For the goods receipt for the scheduling agreement the system displays error M7 064: "Document xx does not contain any selectable items".
Answer:
A possible reason is that the document is subject to a release strategy and has yet to be released. You can check this using transaction ME33 and release it subsequently if necessary.
Another reason can be that although a confirmation control key that contains a confirmation category with GR assignment has been maintained for the scheduling agreement item, this category has yet to be confirmed. You can check this using transactions ME33 and OMGZ. If necessary, create the relevant confirmation.
Another reason may be that no undelivered schedule line exists up to the posting date. If nevertheless you want to post the GR, you can use transaction ME38 to bring the next schedule line date forward, or in transaction MB01 you can select the "Suggest Zero Lines" field or in transaction MIGO the "Propose All Items" field under Settings - Default values.
From the snapshot of the notes 493404 above:
1. I don't have a release strategy for the scheduling agreement. Have checked via ME33L
2. I didn't implement any confirmation control in the scheduling agreement. Have checked via ME33L
3. I've a delivery schedule line up to the posting date. In my scenario, schedule line date = GR posting date
Therefore, I'm still truly puzzle with the system behavior. Any further help will be most appreciated.
Thanks.
Steven

Error generating release against scheduling agreement

Need help in resolving the below error msg for Scheduling Agreement.
ERROR message:
"Error generating release against scheduling agreement (cause 2)"
"2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated."

Yes.. its solved now...
problem areas:
1: delivery date not matching GR date.
solution: chng delvry date to GR date in ME38 and thn do GR.
2: Release not hapnd properly incase if u hav used doc typ LPA for JIT/Forcasting.
solution: in ME84, chk if the indicator for 'create release' is 'green' for ur SA#. In ME38, select the line and click on 'Release" icon. Select ur relevant delivery schudle line and click on JIT release or Forcast Release icon. See if the indicator is 'Green". If not, the issue is wit message output for the perticular delivry date. (use msg typ LPET process for output) MAKE SURE U SAVE THIS CHNG. Chk againg for the Release indicator for delivry line. If green thn.. its done..
Let me know if it was hlpful... or need clarity

Error generating release against scheduling agreement (cause 6) in ME38

Hello Experts,
Need your inputs on the the below error getting generated in ME38
Error generating release against scheduling agreement (cause 6)
Message no. 06857
Diagnosis
The function module for generating a scheduling agreement release (forecast delivery schedule or JIT delivery schedule) has run up against an error, causing processing to be terminated.
In this case the cause of the error is 6.
System Response
The error may involve one of the following situations:
1: The nature of the error cannot be specified precisely.
2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated.
3: A document type for which the functions "Generate forecast delivery schedule" or "Generate JIT delivery schedule" are not defined may be involved.
4: A material for which the function "Generate JIT delivery schedule" is not defined may be involved.
5: A scheduling agreement that has not yet been released by all persons responsible may be involved.
6: The factory calendar has not been maintained correctly.
Procedure
Error source 1:
Check whether the vendor and plant shown in the PO actually exist in the system.
Error source 2:
Check the Customizing facility for message determination with respect to delivery schedules created under scheduling agreements (print operation '9').
Error source 3:
In Customizing, maintain the document types accordingly ( Define document types for scheduling agreement). Then create a new scheduling agreement with a document type for which release documentation is defined.
Error source 4:
Maintain the JIT delivery schedule indicator in the material master record.
Error source 5:
Have the scheduling agreement released by the person(s) responsible.
Error source 6:
If you are using a release creation profile without aggregation, you must maintain the factory calendar for the next 999 days
Regards,
Santosh

Hello Mallinath,
I referred the note and following are the observarion in the system.
Step1:Run T-code SE16 (table T001W) to check the calendar ID of the plant.
-----Referred the Calendor ID
Step2: Check the JIT/Forecast delivery schedule of release creation profile in customizing. (T-code OLME -> Scheduling Agreement -> Maint. Rel. Creation Profile for Sched. Agmt. w. Rel. Docu.)
Run T-code SCAL to adjust the period of the calendar ID which checked in STEP 1 according to the JIT/Forecast delivery schedule of the release creation profile which checked in STEP 2.
(For example, if the JIT/Forecast delivery schedule of the release creation profile is "999" days, then the calendar should be extended for the next 999 days at least)
---------In this case factory calendor is valid till 2015 and according to note needs to change the factory calendor till 2018( or for 999 days) ?
Waiting for your inputs.
Thanking you,
Santosh

Sap Error generating release against scheduling agreement (cause 2)

Hi,
Please help me on this issue
Error generating release against scheduling agreement (cause 2)
Message no. 06857
Regards
Amey

Hi,
For EDI you might be missing settings in:
1) Matrl Mng -> Purchasing -> Messages -> Output control -> Output types -> Define Message Types for Scheduling Agreement Release/Expediter -> Fine-Tuned Control: Forecast Delivery Schedule/Expediter (check one of the outputs for 9 and for A )
2) WE20 - EDI settings for partner that is a vendor who should receive your release information DELFOR / DELJIT (if you do not manage other EDI settings then also other WEDI setings should be maintained)
Best Regards,
Tomek

MIGO against Scheduling agreement.

Hello,
We want to receive material against delivery schedules of Scheduling agreement.
Our setting are.
No MRP
Delivery schedules are created manually.
No confirmatin control.
Issue is, delivery schedules are future date but i want to make MIGO today without changing the delivery schedules in ME38.
Is it standard SAP setting that we will not be able to receive the material for future dates ? or is there some setting in background ?
Sundar

>
GSMY Volvo wrote:
> Hello,
>
> We want to receive material against delivery schedules of Scheduling agreement.
>
> Our setting are.
> No MRP
> Delivery schedules are created manually.
> No confirmatin control.
>
> Issue is, delivery schedules are future date but i want to make MIGO today without changing the delivery schedules in ME38.
> Is it standard SAP setting that we will not be able to receive the material for future dates ? or is there some setting in background ?
>
> Sundar
Its standard SAP setting that migo cannot be done with delivery in future dates. To do migo, change the delivery schedule to today's date and then do the GR against the SA.

GRs created for schedule line of future date

While making Goods Receipts using MIGO transaction, we are seeing tha GRs can be done for scheduling agreements having schedule line of future dates. Is there some way of restricting the GR upto to current date only. Meaning suppose if I have the following schedule lines:
category of delivery date         delivery-date           schedule quantity
M                                               01.2010                   100
M                                               02.2010                    200
M                                               03.2010                    150
Currently the system is allowing to do GRs of quantity = 450 (100 + 200 + 150) in the month of February, 2010.
But I want that while doing a GR in February, 2010 the system should allow to do GR of quantity 300 only (100 + 200). Please let me know how we can do so in the system.
Regards,
Pratima.

Dear Veer,
Your answer has helped in the MIGO transaction. Please let me know if something similar is possible for inbound deliveries also. Meaning like in MIGO transaction, I should not be able to make inbound deliveries (in xns VL31N) for schedule lines of future dates / months.
Regards,
Pratima.

Scheduling Agreement for Imported Material

Hello Friends
I am doing import cycle through scheduling agreement.I maintained all the conditions(custom duty and CVD with custom clearing vendor) in scheduling agreement.Now i am doing first LIV to capture planned delivery cost of bill of entry in t code MIRO for that i am selecting layout as planned delivery cost.but the system gives the error msg as no delivery cost exist for PO 5500000000 (SA number)
Please help me out why system is not recoginizing custom clearing vendor and how to sort this out
Regards
VS

Hello Priyanka,
Following message am getting while doing first LIV for planned delivery cost in case of import process against scheduling agreement.
No delivery costs exist for purchase order 5500000000 00000
Message no. M8014
Diagnosis
You have chosen Delivery costs -> Planned -> By purchase order. This function allows you to process delivery costs which were planned in the puchase order. The purchase order which you are currently processing does not contain any planned delivery costs.
Procedure
Check the purchase order number. If it is correct, you can only post the delivery costs as unplanned delivery costs
Regards
Vivek

Document type LPA in schedule agreement

any one can explain me document type LPA in schedule agreement. I read books as that is document type with release documentation. And what is the diff between LP and LPA?

Dear,
Please find below, which I found by search and posted by fellow collegues earlier....
Default quantity for goods receipt
In the standard system, the quantity open to date from the last- transmitted SA release is used in the case of scheduling agreements with release documentation (document type LPA). In the case of scheduling agreements without release documentation (document type LP), the open quantity to date is used.
Document Type of Scheduling Agreement
As a rule, the APO scheduling agreement in the SAP R/3 system is a scheduling agreement with the document type LP or a scheduling agreement without release documentation.
If you use scheduling agreements of the document type LPA without confirmation control key then no default quantities can be determined from the release upon goods receipt.
If you use scheduling agreements of the document type LPA with confirmation control key then the default quantities from the confirmation (shipping notification) are used.
As a rule, the OLTP scheduling agreement in the SAP R/3 System is a scheduling agreement with the document type LPA.
A scheduling agreement is a longer trem agreement with a vendor covering the supply of materials subject to predefined conditions.The conditions are valid for a pre defined period and a pre defined total purchase order quantity.
You can enter the Target value in the header data of the scheduling agreement.You can enter the Target quantity in the item overview for each item
You can use scheduling agreement with or without release documentation.The advantage of working with scheduliing agreement release documentation is that you always have a record of when you sent which delivery schedule information to your vendor,which you can display at any time.
Without release documentation(Document type LP)
The delivery schedule lines have official character-that is to say,they are transmitted to the vendor as they are saved in the system.The system does not document in detail releases aganist the scheduling agreement that have been sent to the vendor.Therefore,in the case of the document type without release documentation,the message control facility should be set up in such a way that a message is immediately sent to vendor if any changes are made to the delivey schedule stored in the system.
With release documnetation(Document type LPA)
If you use scheduling agreement with release documentation,the delivery schedule lines are not transmitted directly to the vendor.Intially ,the lines of the delivery schedule stored in the system for an LPA scheduling agreement for an internal information only.A message informing the vendor of your material requirements cannot be transmitted to the vendor until you explicitly create an SA release,that is forecast (FRC) or Just in Time(JIT) delivey schedule.Through this process,you can change the way schedule lines are represented.With release documentation,you can disply the SA releases(delivery schedules) transmitted to a vendor over a certain period of any time.This enables you to trace precisely when you sent which information to vendor.
Regards,
Syed Hussain.

Scheduling agreement for customer?

Hi,
Similar to what we have in MM the scheduling agreement, which as i know is the substitute for long term purcahse order.
my question is whether we also have scheduling agreement between firm and the customer simliar to scheduling agreement?
there must be but terminilogy may be different. may i know what we call it SD?
Raj

Dear Friend,
-->Scheduling agreement is one type of outline agreement. (T. Code:- VA31)
-->Scheduling agreement means the agreement between customer and company which is having details about which is the quantity to be supplied for a perticuler date.
-->It is like a cotract but here we will have cofirmed quantity and delivery dates in different schedule lines for a perticuler duration or period.
--> From scheduling agreement we can create delivery directly without sales order.
-->Example -- If the customer specifies the date and quantity of the required material for a specific duration we will create scheduling agreement in the SAP.
Customer 'A' asked the company total required quantity is 100 but he wants supply in four instalments at specific dates in the month of March then we can create scheduling agreement for that requirement and we will supply according to that.
I hope it will help you. Reward points if helpfull.
Dhananjay

SD create Collective delivery document against scheduling agreement.

Dear freinds,
I have created scheduling agreements for single material , and updated forecast deliery agaisnt IDOCS,
now I want to make a single delivery agaisnt four different materials.
I use Transaction VL 10 for Delivery due list and selected diff. materials four items,executed backgroud run,
system is creating two delivery documents instead of one.
Please advise me how to get single delivery document against multiple delivery due items.
in customer master i marked to order combination, partial delivery allowed up to 9 deliveries
Regards
Dilip

Excellent information !
I understood what you have mentioned .
Just I need your clarifications for my below queries to fix this issue .
There are 6 line items in this scheduling agreement .
For 3 line items , delivery schedule date is 02/08/2008 . for another 2 line items, delivery schedule is 05/07/2008 . due to this different delivery schedules for line items in scheduling agreement . whenever user creates delivery , delivery split is happening .
In order to avoid this problem , can ask user to change delivery schedule for another 2 line items to 02/08/2008 from 05/07/2008 . ?
If user change this delivery schedule for this line items , is there any ramification in anyway ?.
Thanks In Advance

Movement Type 351 against scheduling agreement for future dates

Similar Messages

Maybe you are looking for