Difference between capacity formulae and scheduling formulae in workcenter

Hi experts please give me the solution for my queries
1. What are the capacity formulae and scheduling formulae in workcenter, give me examples, What is the difference between capacity formulae and scheduling formulae in workcenter , how these are used in workcenter.
2. what is group and group counter in routing , how these are used in routing , please explain.
3. what is the difference between PRTs created with MM01 AND CF01
4. what is alternative group and order catagery
5. what is system status , user status and authorisation matrix

>
hemamaheswararao wrote:
> Hi experts please give me the solution for my queries
> 1. What are the capacity formulae and scheduling formulae in workcenter, give me examples, What is the difference between capacity formulae and scheduling formulae in workcenter , how these are used in workcenter.
> 2. what is group and group counter in routing , how these are used in routing , please explain.
> 3. what is the difference between PRTs created with MM01 AND CF01
> 4. what is alternative group and order catagery
> 5. what is system status , user status and authorisation matrix
Dear Hemamashewararao,
Welcome to SDN !
As per rules you need to raise only one query as per one thread
Coming to your first query
As per business requirement formula will be defined
The most important difference between Capacity formula and scheduling formula
In SPRO
for scheduling formula tick mark will be marked for scheduling where as for capacity option tick mark will not ticked
For capacity formula tick mark will be marked for option capacity where as for scheduling option tick mark will not ticked
Currently i am not in front of SAP so i couldn't give you path
Good Luck !!!
Regards
Madhu

Similar Messages

"difference between sales order and scheduling agreement "

hi,
i want to know difference between sales order and scheduling agreement and where use scheduling agreement & where sales order ?
please help
amit

Hi Amit,
Its not hard to find this info at help.sap.com
Sales Order
Definition: Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time. The sales area that accepts the inquiry is responsible for completing the agreement.
Scheduling Agreements
Purpose
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.
Integration
You would use this component if you had outline agreements with the customer that contained future delivery quantities of materials that would be sent at certain times within a fixed time period.
If you work with scheduling agreements for the component supplier industry you also need to choose the "Electronic Data Interchange" (EDI) component.

Difference between Purchase Order and Scheduling Agreement

Can any one explain the main differences between a Purchase Order and a Scheduling Agreement?
Thanks in advance

Hi,
A Purchase Order is a document that is given to Vendor to indicate our intention to buy goods from them. It contains what is the desired goods, how much quantity, price, and the delivery date, among other things.
A standard procurement cycle for this is:
PR --> PO --> GR --> IV
A Scheduling Agreement however, is a type of an Outline Agreement. Outline Agreements are divided into 2, first one is Contracts and second is Scheduling Agreement. So this is basically a long term agreement with a particular vendor that contains details on what is the desired goods, quantity, and the exact delivery dates.
A standard cycle for this is:
PR --> Create Scheduling Agreement --> Maintain Delivery Schedule (agreed dates on when vendor will send the goods and time) --> GR --> IV
As you can see, for Scheduling Agreement, PO is not required, but instead we would need to Maintain Delivery Schedule.
Just to share on Contracts, it appears as below:
PR --> Contract Creation --> PO --> GR --> IV
Regards,
Nazrin

Difference between SNP PDS and PPDS PDS

HI Experts.
Can you tell the major differences between SNP PDS and PPDS PDS.
Thanks
Raja kiran R

Hi Raja,
Unlike PPDS planning (time-continuous planning), the least time bucket in SNP planning (bucket oriented planning) is a day, not seconds. Which is why the duration of individual activities in SNP PDS are planned in days only. Scheduling in SNP is based on the fixed duration of an activity and not based on order quantity or capacity load. If a plan contains 3 activities each with fixed duration of 1 day, then the SNP planned order will have duration of 3 days.
On the other hand in PPDS, the duration of an acitivity is calculated based on the resource load that generates the order quanitity, which means larger the qty to be produced, the longer the duration of the activity.
Hope this helps!
Regards,
Umesh

What is difference between SAP R3 And SAP IS Mills Product

HI Friends
What is difference between SAP R3 And SAP IS Mills Product
What are the futures are availables in IS MIlls
Regards

Hi,
SAP R/3 is the central enterprise version. It is not specifically designed for any inducstry sectors and it can cater many of the industry types.
Is is developed for specific industries an for SMB's (small and medium business). It will have components specifically for the industry.
The SAP Mill Products component adds sector-specific functionality to an ERP system to satisfy the complex requirements of mill industries (e.g. metal, wood, paper, textiles, construction materials, and cable sectors).
These industry segments differ from others primarily in that the materials used have a large number of characteristics and variants. The materials in the segments listed above are also predominantly area-based (e.g. paper, textiles, plastic film) or length-based (e.g. cables, piping). Account must be taken of these material characteristics throughout the entire supply chain.
To cater for the particularities of these industry segments, SAP Mill Products features processes and functions that cover the entire supply-chain cycle from product design and configuration, through planning, order processing, capacity planning and production, to final delivery. Additional functions are available in costing and inventory management. SAP Mill Products are also integrated into Quality Management, Financial Accounting, and Controlling.
Prase

What's the difference between the ssd and hd?

I'm in the process of buying a Mac book pro but wanted to know and understand What's the difference between the ssd and hd?

DDHeadley wrote:
What's the difference between the ssd and hd?
HD = hard drive, several metal platters stacked and data read/written magnetically.
Pro's - less expensive and higher capacity of storage. Can scrub the drive of unwanted data. Unlimited write capability.
Con'- bit rot can cause data and operating system to not be as reliable, mechanical moving parts means you can't move the machine while it's on.
SSD = Solid State Disk, basically memory chips that can store data in a permanent fashion without power (like Random Access Memory needs)
Pro's - faster read/write speeds in most cases. Shock resistant makes them ideal for portable uses.
Con's - new technology issues, one cannot securely erase the data on them, unless it's ground into a fine powder. Limited write capability means they will wear out eventually like USB thumb drives do. Wear leveling (TRIM) is used to spread the writes evenly across the drive to maximize it's lifespan.
If you can respect the machine, take care of it and not move it while it's on, or need to scrub the drive of unwanted data, or need higher capacity of storage without paying a fortune for a very large SSD, then a HD makes a lot of sense.
It really comes down to your privacy, do you want a machine you cannot delete files off of?
Do you want to carry around a machine that has all your dirty secrets etched in it for anyone with the right software to uncover?
A computer is a personal machine, why it's called a Personal Computer. We all do things we sometimes are later ashamed of and want to erase all memory of it.
Can't do that with a SSD, it knows all and you will be forced to destroy the machine to rid it of the unwanted data.

EXACT DIFFERENCE BETWEEN FULL LOAD AND REPAIRFULL LOAD?

HI Champ,
Can anyone explain me the exact difference between full load and Repairfull load?Give e some senario where we can go for this?Please.....
10zin

Hi,
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets."
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
repair full request
Re: Repair Full Request
Thanks,
JituK

Difference between f-28 and f-22

Hi Every body
Can i know what is the difference between F-28 and F-22

Hi ,
These t codes are related to FI Module.Plaese post the questions in appropriate forum only.
F-28:POST INCOMING PAYMENTS :Use this transaction to post sponsor payments wired to MIT's bank account. The transaction clears sponsor invoices automatically.
F-22:Enter Customer invoice:Header data :You can use this transaction to enter a customer invoice manually (but you should not use it to enter cost reimbursable or advance scheduled bills unless you are creating a final bill) .
Hope it helps.
Regards,
Pasapula.

Difference between sales document and sales document Header

Hi everyone,
what the difference difference between sales document and sales document Header if look at this equation
VBBE-VBELN= VBAK-VBELN
VBBW is sales document requirement
VBELN is a sales document
VBAK sales document header
then what the difference ales document and sales document Header
kindly assist me to guide the differences
thanks

hi
SAP has differenciated various sales scenarios into various salses documents. basing on the scenario & circumstances you will be having a sales document to use.
sales document header:which carries the properties of a sales document lie CMR MMR CMIR & Pricing conditions etc...
this will be applicable to entire sales document
by sales document we mean the total data carried by a particular document - header; item & schedule line data. each carries its own information to complete the sales document with out errors.
VBBE-VBELN= VBAK-VBELN stands for schedles in the sales order document & document header.
hope this clears your issue
balajia

Difference between ipod video and a ipod v2

can anyone tell me the difference between ipod video and a ipod v2 video?

Brighter Screen
Longer Battery Life
New Search Feature
"Largest" model is available with an 80GB capacity instead of a 60GB capacity.

(261680070) Q WWO-13 What are the difference between WLS6.1 and WLS7.0 web services?

Q<WWO-13> What are the difference between WLS6.1 and WLS7.0 web services?
A<WWO-13> The differences are huge, so different in fact that 6.1 web services cannot
be deployed in 7.0. WLS7.0 and Workshop have much greater functionality than the
limited stateless session (RPC-style) and JMS destination (MSG-style) approach of
6.1. Workshop web services can interact with any type of EJB, any JMS destination
as well as other web services and directly accessing databases. The framework for
building the web service is better and more adaptable and Workshop provides a fully
integrated develop, deploy, test and debug environment. Additionally, WLS7.0 have
the capacity to be much better at performance since due to XML parser enhancements
and the addition of XML maps.

If you want to take existing WLS6.1 web services and convert them to WLS7.0 you can
do so quite easily. The WLS7.0 Ant still supports wsgen so you do not need to even
change your build.xml file. The generated web service however will be implemented
is a manner compliant with the WLS7.0 environment. More details are at:
http://e-docs.bea.com/wls/docs70/webServices/anttasks.html#1070576
"Adam FitzGerald" <[email protected]> wrote:
>
Q<WWO-13> What are the difference between WLS6.1 and WLS7.0 web services?
A<WWO-13> The differences are huge, so different in fact that 6.1 web services
cannot
be deployed in 7.0. WLS7.0 and Workshop have much greater functionality
than the
limited stateless session (RPC-style) and JMS destination (MSG-style) approach
of
6.1. Workshop web services can interact with any type of EJB, any JMS destination
as well as other web services and directly accessing databases. The framework
for
building the web service is better and more adaptable and Workshop provides
a fully
integrated develop, deploy, test and debug environment. Additionally, WLS7.0
have
the capacity to be much better at performance since due to XML parser enhancements
and the addition of XML maps.

Difference between PA_TASK_PUB1 pacKage and Project Foundation API

Whats the difference between PA_TASK_PUB1.update_tasK and the UPDATE_TASK in Project Foundation API?
Im looKing for a concrete documentation how to update tasKs (uppdate schedule and actual dates) from PL/SQL API's.
I already have PA_TASK_PUB1 put in place by a consultant worKing but i do not have an offiicial documentation.
What i have is the documentation on the Project Foundation API, which is not the same as PA_TASK_PUB1.
thanKs.

Yeap. I checked on the Integration repository and indeed PA_TASK_PUB1 is there. But I only knew about PA_TASK_PUB1 because it was used by the Consultant in his codes. Its more of a reference.
what I'm looking for is an official guide on how to manipulate Tasks / project from PL/SQL, and I thought the Projects API in Oracle documentation website which is available publicly is the official (Project Foundation API) one. And then when I saw another PL/SQL package (PA_TASK_PUB1) that was not in the Projects API, I got confused as there might be another documenatation that I miight be missing out.

Difference between parallel sequence and parallel operation in a routing.

Hi Experts,
Can any one explain me with example the difference between parallel sequence and parallel operation in a routing? wHEN CAN WE USE PARALLEL OPEARTION AND PARALLEL SEQUNCE WITH COMPONENT ALLOCATION.
Regards
Deepak sharma

I think u need to modify ur quest... i think u r asking about Parallel sequence and alternate seq. Below are the details from SAP site.
A parallel sequence enables you to process several operations at the same time.
You use an alternative sequence for example, if
--The production flow is different for certain lot-size ranges
For instance you can machine a work piece on conventional machine or on NC machines. A NC machine has a longer set-up time than a conventional machine. However the machining costs are considerably less. Therefore whether you use NC machines will depend on the lot size.
---The production flow changes under certain business conditions.
For instance, if you have a capacity problem, you have some production steps performed externally by a vendor.

Whts the difference between call transaction and session

hi,
can u plz tell me the differnces between call transaction method in BDC and session method.
my doubt is even the call transaction method also can me scheduled using job scheduler then why do we need session method

Hi
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
<b>Reward points for useful Answers</b>
Regards
Anji

Difference between transaction LT11 and VL06C

Hello,
Could you please let me know difference between transaction LT11 and VL06C ? Whether LT11 can be scheduled in background job in place of VL06C.

Hi..
You are absolutely correct. If u want to set up a background job for TO confirmation u can do it in t-code VL06C...
Apart from that in LT11 you can confirm for a sinle TO only..but in VL06C you have wide options to select the confirmation TOs of deliveries based on Fwd agent..WH nos..picikn/packing staus..etc., Click on All secections(+) option in VL06C to get more selection parameters..
Reg,
JJ
Edited by: Jagsap on Apr 15, 2010 12:59 PM

Difference between capacity formulae and scheduling formulae in workcenter

Similar Messages

Maybe you are looking for