Scheduling Agreements configuration steps required Plz !

Dear Sapients,
I request you all to help me in providing the configuration steps for Scheduling Agreements and relevant Schedule lines configuration.
Its urgent please help me !!
Regards,
Sreedhar.

Hello,
please have a look at the following links:
http://help.sap.com/saphelp_media472/helpdata/EN/dd/56078c545a11d1a7020000e829fd11/frameset.htm
and
http://help.sap.com/saphelp_media472/helpdata/EN/da/76ab04ebea11d1954900a0c9306667/frameset.htm
I hope that you find here all information which you want.
Regards
Claudia

Similar Messages

Scheduling agreement configuration??

hii
Can anybody explain me on below things
1.Scheduling agreements configuration steps..??
Configuration steps for below process:
Without release documentation (in the standard system, document type LP)..??
With release documentation (in the standard system, document type LPA)..???
Thnaks
SAP-MM

Hi,
First Define Time Dependent or Not Depenedent via
In the case of scheduling agreements and quotations, the document type determines whether time-dependent or time-independent conditions can be created. You can set the Time-Dependent Conditions indicator in Customizing for the document type to enable time-dependent conditions to be maintained in scheduling agreements and quotations.
Define time-dependency in scheduling agreements and quotations:
SAP Customizing Implementation Guideu2192Materials Managementu2192Purchasing u2192 RFQ/Quotation or Scheduling Agreement u2192 Define Document Types
and document type is
Define document types for scheduling agreement:
SAP Customizing Implementation Guideu2192Materials Managementu2192Purchasing u2192 Scheduling Agreement u2192 Define Document Types
For release u can create Release profile
Create release creation profile:
SAP Customizing Implementation Guideu2192Materials Managementu2192Purchasing u2192 Scheduling Agreement u2192 Maint. Rel. Creation Profile for Sched. Agmt w. Rel. Docu.
You can use release creation profiles to define the criteria for the creation of SA releases (you can influence the quantities and delivery dates/times to be transmitted to the vendor, for example).
Whether or not you can generate both forecast and JIT delivery schedules against a scheduling agreement with release documentation is determined by the JIT delivery schedule indicator in the material master record. In order for you to be
able to work with JIT schedules, the JIT delivery schedule indicator must be set in the material master record (Purchasing or MRP 2 view) and in the additional data for the scheduling agreement item. No JIT delivery schedules can be created unless this indicator has been set.
Hope Help U !
Regards,
Pardeep Malik

Configuration steps required in ID

Hello Experts,
I am new in XI/PI. Can anyone explain me the configuration steps required when we have one sender and multiple receiver.
I have a scenario having file as a sender and JDBC,File and JMS on receiver side.
If anyone have the screenshot for similer scenario will be more helpful.
Regards,
Jay.

Hi,
in ID, you will need...
1) 1 receiver determiantion
2) 3 interface determination
3) 3 receiver agreement
4) 1 sender agreement
5) 1 sender and 3 receiver channel
Regds,
Pinangshuk.

What are the configuration steps required ?

Hi
Gurus,
Client requires:
"We have construction going on at our warehouses and the projects are going
to take about a year. We need to track retainers on the payments we make to the contractor.
Payments are due in a couple of weeks and it is a priority to monitor progress on the construction."
Example:
                                                                GL Account#
Debit Construction In Progress                      122000          100%
Credit Vendor                                                601095            90%
Credit Accounts Payable / Retainage            202000            10%
At this time we have a request for a solution to process what is necessary
to compile with the following scenarios.
what are the configuration steps required.
Thanks
Anil

Hi,
Whether the contractors are treated as one time vendors or regular vendors. If you have to create new account group for subcontractors
Does only one account group related vendors need the retainage analysis or for all the vendors. Will be mainly the general contractors at each location One group is sufficient even they are at different location you can maintain the same in REGION
Does only single partial payment exists and the remaining due amount to be treated as due on a particular date or multiple payments exists against the same invoice. The 10% must accumulate in a liability account over the life of the contract and is paid at the end. There may be multiple of payments which you need to knock off against the service entry sheet(study above reply)
The construction cost which is treated as outstanding to Vendor to be exclusive of the cash expenditure made for such construction. Yes, but the entire 100% needs to debited to CIP Until and unless the work is not completed so how you can treat as outstanding payment to vendor. If you want you can maintain a provision for this
Check with above and above replies.
Regards,
Sankar
Edited by: Durgasankar.Innamuri on Jul 29, 2010 10:17 AM

CIN-MM Configuration steps required for First Stage Delaer purchases.

Hi,
I am looking for CIN-MM Configuration steps required for First Stage Delaer purchases.
We have steps Configured for CIN-MM from Manufacturer for purchase of Materials and Capital Goods.
Thanks in advance.
Regards,
Purna.

Hi Purnachandrarao... ,
There is no seperate configuration required in dealer's case.
For this you have to use zero Tax code.Material should be maintained in J1id.
So that Tax % will be picked up from there.
But at the time of GR you have to tick MRP indicator in excise tab.
And also you have to change values of BED and cess as per vendor's invoice.
So that value will be fetched at the time of invoice verification.
Regards,
Gitesh

Transportation Configuration Steps required:

Hi Guru's
I am new to this module, could you please show the configuration steps for the SD- Tranporrtation module please.
sushil

Hi Sushil,
TMS Total steps:
3.     Terminology:
Mentioned below are some important terms used in Transportation:
SAP Terminology:                Description
1. Forwarding Agent:                Agent who provides the transportation
2. Transportation Planning Point :      Org. unit responsible for planning shipments with particular features. E.g.: A company has different groups of shipping personnel responsible for organizing shipments by train or ship
3. Shipment Document:     The document containing the details of the deliveries, service agents
, routes, stages, planning and execution times.
4. Shipment Type:     Shipment types contain all the essential control features for the shipment document such as number ranges, service level, and output and partner determination.
5. Routes:     The route determines the itinerary and the means of transport in shipping, and influences transportation scheduling.
6. Shipment Cost Document     The shipment cost document is the used for shipment cost processing. It contains the details related to accounting and the cost calculations.
7.Shipment cost type and item categories     Shipment cost types and item categories contain all the important control features for the shipment cost document, such as number range, status requirements for the shipment documents, and parameters for shipment costing, parameters for shipment settlement.
8. Master Data:
Purchase Order is created for Vendor if the weekly or monthly orders are not created during the transaction by the system.
Relevant pricing conditions are maintained.
9. Customization:
1. Transportation Relevance is marked for Delivery type, Delivery Item Type,   Route.
2. Route Determination is active.
3. Route is determined in the delivery document.
4. Shipment types are created as desired.
5. Shipment pricing procedure is in place.
6. Shipment cost types are created and assigned to shipment types.
7. Purchasing Data is assigned.
8. G/L Account assignments are done.
10. 1.Maintain Transportation Planning Point
The transportation planning point represents a group of employees responsible for organizing transportation activities. Each shipment is assigned to a specific transportation planning point for transportation planning and shipment completion
The transportation planning point is assigned at Co-Code level.
Menu Path: Enterprise Settings > Definition > Logistics Execution > Maintain transportation planning point
10.2.Define Routes
The route determines the itinerary and the means of transport in shipping, and influences transportation scheduling. The description of routes, service agent, distance and lead times are defined in routes.
Menu Path: Logistics Execution > Transport > Basic Transportation Functions > Routes > Define Routes > Define Routes And Stages
10.3.Maintain Route Determination:
Routes are determined depending on the following criteria:
1.     Country and departure zone (departure zone of the shipping point)
2.     Shipping conditions agreed in the sales order.
The shipping condition is defined in shipping point determination.
3.     Transportation group of the material
4.     Country and transportation zone (receiving zone) of the ship-to party
Menu Path: Logistics Execution > Transport > Basic Transportation Functions > Routes > Define Routes > Route Determination > Maintain Route Determination
10.4Maintain Transportation Relevance
Delivery types and delivery item categories for which transportation processing is to be carried out must be characterized as relevant for transportation.
All routes that are to be used for the shipment must also be set as relevant for transportation.
Menu Path: Logistics Execution > Transport > Shipments > Maintain Transportation Relevance
10.5.Define Shipment Types:
The shipment types represent the different forms of transportation processing in sales and distribution.
The following forms of transportation processing are distinguished:
1) Individual shipment, one or more deliveries are transported by a single mode of transport from one point of departure to one final destination.
2) Collective shipment, one or more deliveries are transported by a single mode of transport from one or more points of departure to one or more final destinations.
3) Multimodal shipment, deliveries are transported by several modes of transport between one or more points of departure and one or more final destinations.
Menu Path: Logistics Execution > Transport > Shipments > Define Shipment Types
10.6.Define Shipment Cost types
10.7.Pricing
Logistics Execution > Transport > Shipment Costs > Pricing > Pricing Control > Define And Assign Pricing Procedures
10.8 Settlement

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

Subcontracting through scheduling Agreement

hi ..
helloo..i want to knw the steps by step procedure for the subcontracting using scheduling agreement..
thanks..
Rgrds,
AVS

Hi
Steps are the same as how you create for a SC PO and the creation of shedule lines is the same standard way. Only the item category will be L - Subcontracting.
To enter several delivery dates for a subcontract order item, proceed as follows:
Display the scheduling screen for the item.
Enter the quantities and dates.
If the ordered material has a bill of material, the components are copied from the bill of material.
If you do not use bills of material, you must either enter the components manually or refer to an existing purchase requisition. You have to enter the components for every delivery schedule.
Position the cursor on a schedule line and choose Item ® Component ® Overview to display the screen for processing components. You can enter or change the individual components in the same way as an order item.
To make entering the schedule lines easier, copy the components for other delivery schedule items. To do this, select Edit ® Repeat components ® Activate.
When you enter the next delivery schedule for the material, the components will be copied from the selected delivery schedule. The quantity and the date required are redetermined.
Save the delivery schedule.
When you print the scheduling agreement, the quantity required per component and date required are reprinted.
Thanks & Regards
Kishore

Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

PBXX pricing issue in Scheduling agreement

Hello,
We have a procedure to enter the price in Scheduling Agreement manually but required to store the value in PB00 condition type instead it is showingup in PBXX..We want value to be update in PB00, is there any standard SAP setting to be done in condition type..?
Thanks
Ranjit

Hi,
Please check what access sequence maintained for PB00 and PBxx will be added manually only and will not have access sequence.
Please check the condition type and condition record the PB00 condition is with access sequence so it will identifies the values recorded in contract and inforecord
while PBXX dont have access seq u have to put values manually
check the PB00 PBXX and access seq given in PB00 u will get the idea
Regards,
Ninad Kshirsagar

Procedure of scheduling agreement with jit

Can any one explain the step by step by procedure of creation of scheduling agreement with jit(just in time)
Vasu,K

Dear vasu,
The steps are
Step 1: Create Creation Profile in IMG under Scheduling agreement node
Step 2: Assign that creation profile to Material in the material master and the JIT indicator
Step 3: Ensure that creation profile copied to the SA, if not then assign it in the item detail
Step 4: Then run the Transaction for the delivery shedule creation
Ste 5: Check the shedule created
Thanks,
With regards,
Krishna Reddy

Configuration steps for Extended Classic Scenario

Hi All,
Could you please let me know what are the configuration steps required for extended classic scenario.
Thanks in advance

Hi,
Important Settings that Determine the Extended Classic Scenario
The following settings are required for the extended classic scenario:
u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
This is for your additional information.
Hope this helps.
Regards,
Vikas

Scheduling agreements in MTO production process

Hi All,
Client requirement is to map scheduling agreements in sap and for that scheduling dates MRP need to run. My question is, is it required to create sales order with reference to scheduling agreement or not. Because they have Make-to-order production scenario.
Regards
Chowdary

Hi Chowdary,
No need to create sale order for scheduling agreement, because the schedule lines are being finalized at scheduling agreement level only,so we do delivery according to delivery schedule with reference to the schedule agreement number.
As per my knowledge in make to order scenario also we can execute from scheduling agreement,your material requirement will be transferred according to that they do production as per the product availability you will schedule the deliveries.
Regards
Ram

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

Configuration steps to Trigger IDOC from R/3 to XI

Hi All,
I have read several forums ,
and i am in confusion to follow which one of them.
Let me describe the process of configuration steps in r/3 and XI in step by step and correct me when i am wrong.
Steps in R/3
1) Goto SALE.
   Basic settings->Logical Systems->Define logical system.
   Create two logical systems(one for XI and the other for R3)
   Basic settings->Logical Systems->Assign logical system to client.
   Assign the R3 logical system to respective client.
   Assign the XI logical system to respective client.
Whether i need to create logical sys name only for r/3 or both for r/3 and XI?
2)Goto SM59.
   Create new RFC destination of type 3(Abap connection).
   Give a suitable name and description.
   Give the Ip address of the XI system.
   Give the system number.
   Give the gateway host name and gateway service (3300 + system number).
   Go to the logon security tab.
   Give the lang, client, username and password.
   Test connection and remote logon.
   Gateway service can be sapgw<sys number> or it should be 3300+sys number?
3)Goto WE21.
    Create a port under transactional RFC.(R3->XI)
    Designate the RFC destination created in prev step.
   Port name should be in the form of SAP+SID of XI or it can be anyting?
4) Goto BD64.
   Click on Create model view.
   Add message type.
   Is it necessary to create a Distribution model and distribute it ?
5) Goto WE20
    Goto WE20.
    Partner type LS.
    Create a partner profile
    Give the outbound or inbound message type based on the direction.
Steps in XI
1) Goto SALE.
   Basic settings->Logical Systems->Define logical system.
   Create one logical systems(only for R3)
   Basic settings->Logical Systems->Assign logical system to client.
   Assign the R3 logical system to respective client.
Whether i need to create once again logical sys name for r/3 ?
2) Goto SM59
   Create new RFC destination of type 3(Abap connection).
   Give a suitable name and description.
   Give the Ip address of the XI system.
   Give the system number.
   Give the gateway host name and gateway service (3300 + system number).
   Go to the logon security tab.
   Give the lang, client, username and password.
   Test connection and remote logon.
   Gateway service can be sapgw<sys number> or it should be 3300+sys number?
3)Goto IDX1.
    Create a port under transactional RFC.(XI->R3)
    Designate the RFC destination created in prev step.
   Port name should be in the form of SAP+SID of R3 or it can be anyting?
Step 4)Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Is it neccessary to create a medata?
Let me know the answers for my questions.
Thanks
Sai

Not sure what you have referred till now but there are some excellent link that will close this for you.
ALE configuration for pushing idocs from SAP to XI -
ALE configuration for pushing idocs from SAP to XI
Configuration steps required for posting idoc's(XI) -
Configuration steps required for posting idoc's(XI)
Wiki: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

Scheduling Agreements configuration steps required Plz !

Similar Messages

Maybe you are looking for