BTO,BTS,CTO and ETO Manufacturing Scenarios impacting MES or not?????????

Hii Everyone...Wish u all a very happy new year 2011.CAn u all pls help me get some informations on different manufacturing startegies and regarding the same my query is mentioned below:-
How does different manufacturing Scenarios like BTO,BTS,CTO and ETO impact implimentation of MES system.
How is the interface of MES with ERP,LIMS,PDS,PLM,Equipments and SCM,CRM systems.Whether the interafce changes considering the scenarios like ETO,BTO,BTS,CTO.

Hi KRajiv,
I would say that either of those production strategies can be maintained in SAP ME solution, however, this tool is responsible for technical implementaion of the strategy rather then for its design. So, you will not find a document with step-by-step instructions for each of those strategies with pointing to difference between them.
Currently, SAP ME has interface with ERP only.
I would suggest that you consult "Business Scenario Description SAP ME 5.2" available on SMP:
https://websmp209.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000722058
Regards,
Sergiy

Similar Messages

How MES is effected with BTO,BTS,CTO and ETO manufacturing scenarios.

Does MES really gets impacted with following different manufacturing styles like BTO(Build to Order),BTS(Build to Stock),CTO(Configure to Order),ETO(Engineering to Order)...Whether SAP ME(different/latest versions) handles its separately if the production is happening as per BTO,BTS,CTO,ETO scenario.
If its affecting MES then how it does it and how the integartion with different systems ERP,PLM,PDM,LIMS,SCM is dealt in each scenario .

Manufacturing Execution Systems (MES) are IT solutions that support the primary production processes in a production plant. These applications close the gap between ERP systems and production equipment control or SCADA (Supervisory Control And Data Acquisition) applications.
MES will be used to pass the real time Data in Shop floor in to SAP,
In SAP ME
Master data:
Master data detail is transferred from SAP R/3 to SAP ME, data such as material master, BOM, routing, Production order is transferred from r/3 to SAP ME thru IDOC/BAPI
Transaction data:
Real time data is Collected from the SCADA or from controller is send to SAP ME, From SAP ME, the data is transferred to R/3 by using BAPI/IDOC
separately if the production is happening as per BTO,BTS,CTO, ETO scenario
while transferring the prdn order from R/3 you can also send infrm such as Customer/project

How to identify difference between Configure To Order (CTO) and Engineer To Order (ETO) items

Hi All,
We are working on Oracle Database 10g
We have to develop a code which involves Configure To Order (CTO) and Engineer To Order (ETO) items.
Can anyone advise is there any table and the corresponding column in the database which will help identify if an item is a CTO or ETO.
Regards,
Shruti

Shruti,
Have you checked eTRM website? -- http://etrm.oracle.com
Please also see (How To Find the VIEW or TABLE That Populates a Form So That a 'Custom Report' Can Be Created Using Same VIEW or TABLE (Doc ID 604772.1)).
Thanks,
Hussein

Switch from classic to Extended Classic Scenario- Impact

Hello,
We are proposing to switch from Classic to Extended Classic Scenario.
We are on SRM_SERVER 550,Sp7 and SAP 4.7 backend.
We want to know if this is technically feasible to switch and have less/no impact on existing transactional data and master data.
Main concerns are: Existing open Shopping carts and PO's.
We are also modifying the WF by including buyer completion WF.
Will the carts created in classic scenario and 'awaiting approval' work similarly in ECS?
Can we copy old carts (created in classic scenario) into new ones in ECS?
Are there any other issues like the ones above which people have come across?
Is there any standard SAP material/Consulting note available
which gives some guidelines for switching scenarios?
Regards,
Srivatsan

Hello,
You can switch from the classic to the extended classic scenario by making the global settings in the IMG.
But it would be better if you can decide if only a particular set of categories need ECS.
If you wish to have both the scenarios,the deciding factor is the product category.
You can also activate a BADI for the control of ECS despite the above Global settings.
Reward if answer is helpful,
Thanks & Regards,
Nagarajan

ISE admin , PSN and monitoring node fail-over and fall back scenario

Hi Experts,
I have question about ISE failover .
I have two ISE appliaces in two different location . I am trying to understand the fail-over scenario and fall-back scenario
I have gone through document as well however still not clear.
my Primary ISE server would have primary admin role , primary monitoring node and secondary ISE would have secondary admin and secondary monitoring role .
In case of primary ISE appliance failure , I will have to login into secondary ISE node and make admin role as primary but how about if primary ISE comes back ? what would be scenario ?
during the primary failure will there any impact with users for authentication ? as far as PSN is available from secondary , it should work ...right ?
and what is the actual method to promote the secondary ISE admin node to primary ? do i have to even manually make monitoring node role changes ?
will i have to reboot the secondary ISE after promoting admin role to primary ?

We have the same set up across an OTV link and have tested this scenario out multiple times. You don't have to do anything if communication is broken between the prim and secondary nodes. The secondary will automatically start authenticating devices that it is in contact with. If you promote the secondary to primary after the link is broke it will assume the primary role when the link is restored and force the former primary nodes to secondary.

Suggest manufacturing scenario Discrete / Repetitve for Iron & Steel indus

Which scenario u will suggest for Iron & Steel industry & why?
Product - Galvanised Plain/ Galvanised Corrugated Sheets
Process- Pickling-Cold Rolling -Galavanizing- Cutting /Corrugation
but the product is varying in THK & Width so how u can go for repetitive?it works on both scenario MTO & MTS
yes sheets r of diff sizes & widths as per orders but same operation is carried out but u have control some parameters
Kindly suggest manufacturing scenario Discrete / Repetitve ?

Hi
If u say that the sheets are of different sizes and shapes, will the different sizes have different workcenters or in one machine all the different sizes can be produced. if all the sizes and shapes come out of the same machine, i think discrete will be the best suited(as per my knowledge) or if only the last operation of cutting is different and other operations are same, then u can go for the combination of Repetitive and discrete.
Chandra

Evaluation Structure for Production Order and Repetitive Manufacturing

Dear PP friends,
I am trying to create a Evaluation Structure with reference to an Evaluation Structure (t-code MCR7). I need to join the Standard Evaluation Structures S021 (Production Order) and S026 (Material Usage), but S021 is not appearing to choose characteristics and key figures.
Does anyone have suggestions?
My requirement is to create a report where I can see goods receipt x goods issues per order.
Thanks in advance.
Marcos

Hi,
As we know that In Repetitive Manufacturing, components are often staged at the production line without reference to a particular order.
To create the demand program again for your production order, you must define the planning strategy for a product. Planning strategies represent the methods of production for planning and manufacturing or procuring a product. and run the scenario accordingly.
Regards
Chandra

Difference between repetative manufacturing and discreate manufacturing

Hi,
Guru's
What is the difference between repetative manufacturing and discreate manufacturing in product costing.

Dear Manish,
Repetitive Manufacturing
In repetitive manufacturing, master plans are typically created on a period and quantity basis (reduction in individual lot and
order-specific processing). A quantity of one product is manufactured over a certain period. The product is processed in a constant flow and interim products are generally not stocked. In repetitive manufacturing, you usually find that the effort required for production control is significantly less than is required for single lot and order-based production control and the recording of actual data is kept simpler. Repetitive manufacturing can be used for various industries, such as the
consumer packaged goods industry, the electronic industry, packaging industry, for example.
You can use Repetitive Manufacturing purely for make-to-stock production, or in a sales order-oriented environment, such as found in the automotive industry.
Discrete Manufacturing
Discrete manufacturing is characterized by requirements that occur on an irregular basis and a workshop-oriented process.
The Discrete Manufacturing scenario can be used in different variants, production by lot size, make-to-order production and assembly processing. The variants differ mainly in the type of planning conducted before-hand and in the relation to the sales order. Production by lot size is identified by the grouping of requirements into lots during requirements planning, and by planning with existing basic data. Production by lot size is independent of a particular sales order. Make-to-order production describes the production of a material with reference to a particular sales order. The manufactured quantities are managed, in terms of stock, directly for the individual sales order. They cannot be exchanged with the stock of other sales orders. Starting from the sales order, single-item planning can be allowed as far down the bill of material (BOM) structure as you like. Assemblies and
components can also be procured for the sales order that generates the requirements, and managed in stock for this sales order. If the product is a configurable product, the system chooses a variant for the customer based on the characteristics that he or she selects. A sales order BOM can then be generated for the sales order. This BOM is used to produce the product.
Assembly processing is a form of make-to-order production, in which the production order (assembly order) is created together with the sales order. In assembly processing the components for the product have, in general, already been produced. They only need to be assembled. The advantage of assembly processing is that an availability check is carried out for the components when you create the sales order. This increases the reliability with which dates can be confirmed
considerably. Changes to the sales order are automatically also made in the production order and vice-versa.
And also you can follow the below link to know more about REPITITIVE MANUFACTURING its a pdf document from help.sap.com
http://help.sap.com/printdocu/core/print46c/en/data/pdf/PPREM/PPREM.pdf
One More Example
Repetive is usually a continuos flow, good example is making 5000 tv dinners you know how long it takes to make qty1 very little defects or fall out and you always have everything on hand to start the run, you may also make the same run 2-3 times per month so a cost collector is ok all cost go to top level.
Discreet, You do have falls out reworks and move into production missing materials, long lead time its essential to know what and where it is at in production, cost may vary a little but each production order will be costed independantly for review.
Best Regards
Mir
Edited by: mirosmank on Dec 28, 2010 11:25 AM
Edited by: mirosmank on Dec 28, 2010 11:28 AM

How to club the downpayment and periodic billing scenario in Sales Order

Hi experts,
Could you please let me know how to club the downpayment and periodic billing scenario in Sales Order.
Requirement is : If you have 10 lacs total amount and out of that 50% should be the downpayment and rest of the amount should be distributed among three equated instalments for 2 months each (periodic billing). This should work with one line item in sales order. Pls provide relevant inputs how to work out this scenario.
Your help would be appreciable.
regards....Diwakaran

Hi Yang,
Workflow is the best approach for any issue related to business objects.
Since you want call FM BAPI_SALESORDER_CHANGE, it will change SO. It means everytime any SO is changed there will an event being triggered.
object type: BUS2032
event: Changed
simple solution:
1. Please create object type (SWO1) and its super type should be BUS2032.
2. Add your own method and attach your custom FM which actually updates the qty & PR)
3. Create Task (PFTC_INS)
in basic data:
- provide object type which you have created
- provide method which you have added
goto triggering events tab
- Choose Object Category as BOR object type
- provide object type (better give BUS2032)
- provide event as CHANGED
Please have look into very nice video blog which helps you to create your workflow.
blog: [Creating your first SAP Business Workflow]
Regards,
Sukhbold Altanbat.

Clarifications on EBP-SUS and MM-SUS Scenario

Hi !
We are planning to implement EBP-SUS and MM-SUS in one Client . Request you to help us on the following issues.
1. While the outbound messages will not have a problem from MM & EBP, how do we route inbound messages to MM & EBP effectively. Should be handle it in XI ?? If ues, what is the best criteria .
2. Since both the config guides for MM-SUS and EBP-SUS scenarios include transactions for transferring Vendor & Comapny Code data, how do we check duplication.For ex : if we transfer a Vendor from R/3 and subsequently try to transfer the same vendor from EBP , is there any inbuilt duplicate check ?
3. In MM-SUS, an ASN created in SUS creates an inbound delivery is created in MM. What would happen in case of EBP-SUS i.e when an ASN is created for an EBP PO ? We are on extended classic scenario ?
4.If you do a confirmation in EBP-SUS, will a GR be generated in both EBP and subsequently in MM.
Request yr help pl.
Regards

Hi
Welcome to world of SRM.
I guess, you must have got enough details in the SRM guides.
Anyways, better to understand the basics first,, before going in detail. I hope this will answer all your queries.
Refer to these links ->
Supplier Enablement
http://help.sap.com/saphelp_srm50/helpdata/en/cd/0e343e47fd6b2ee10000000a114084/frameset.htm
SUS-EBP Scenario
http://help.sap.com/saphelp_srm50/helpdata/en/06/0f343e47fd6b2ee10000000a114084/frameset.htm
SUS-MM Scenario
http://help.sap.com/saphelp_srm50/helpdata/en/39/0f343e47fd6b2ee10000000a114084/frameset.htm
Supplier Self-services
http://help.sap.com/saphelp_srm50/helpdata/en/25/99b13c48740d55e10000000a114084/frameset.htm
Procurement
http://help.sap.com/saphelp_srm50/helpdata/en/8e/e5623c046a9b67e10000000a11402f/frameset.htm
Users in SRM user Management
http://help.sap.com/saphelp_srm50/helpdata/en/cd/6313513813554e941a02a91540c29e/frameset.htm
Please try this SAP OSS notes as well to get System architecture details->
Note 982871 - Consulting services: supplier integration in SRM
963000 - Usage and release of SRM as AddOn to ECC in ERP2005
868192 - Consulting solution: SUS-MM (SUS-MMSRV) service procurement
573383 - EBP and SUS deployment variants
Also do read this ->
Check whether the roles delivered by SAP meet your requirements. If not, you can create new roles and assign transactions to them. We recommend that you copy standard roles and tailor them to your requirements.
All users assigned to a respective role are then allowed to carry out the transactions. If required, you can refine the authorization check on the tab page Authorizations.
Standard SAP Single-roles
SAP_EC_SUS_ADMIN_PURCHASER (for purchasing administrators - SAP Supplier Self-Services)
SAP_EC_SUS_BIDDER (for bidders - SAP Supplier Self-Services)
SAP_EC_SUS_DISPATCHER (for dispatchers - SAP Supplier Self-Services)
SAP_EC_SUS_INVOICER (for invoicers - SAP Supplier Self-Services)
SAP_EC_SUS_ORDER_PROCESSOR (for order processors - SAP Supplier Self-Services)
SAP_EC_SUS_MANAGER (for managers - SAP Supplier Self-Services)
SAP_EC_SUS_SERVICE_AGENT (for service agents - SAP Supplier Self-Services)
If you want to use SAP Supplier Self-Services, proceed as follows:
1. Select one of the following single roles:
SAP_EC_SUS_ADMIN_PURCHASER
SAP_EC_SUS_ADMIN_VENDOR
SAP_EC_SUS_BIDDER
SAP_EC_SUS_DISPATCHER
SAP_EC_SUS_INVOICER
SAP_EC_SUS_MANAGER
SAP_EC_SUS_ORDER_PROCESSOR
SAP_EC_SUS_PRODUCT_MANAGER
SAP_EC_SUS_SAR_PROCESSOR
SAP_EC_SUS_SERVICE_AGENT
SAP_EC_SUS_SERVICE_MANAGER
2. Choose Change Roles.
3. Choose the Personalization tab page.
Note: The personalization applies to all roles, meaning the user can also create his own roles, for example copying the delivered SAP SUS roles. He can tailor these roles to his requirements by changing the SUS-specific attributes (BBP_SUS_ROLE_ATTRIBUTES).
1. Select the entry BBP_SUS_ROLE_ATTRIBUTES (SUS-specific role attributes).
2. Choose Change values.
A dialog box for maintaining SUS-specific roles appears.
3. If required, perform the following steps:
If the role should be displayed in the SUS User Management (UM) and should be able to be assigned to the relevant user by the supplier administrator, set the indicator to display the role in SUS UM.
If the user should be displayed as a service agent for the purchaser, set the Service agent indicator.
If you want to define the user as an SRM administrator, set the SRM administrator indicator. The user is then authorized to change all supplier data.
If want to assign the role SUS administrator automatically to the user during registration, set the SUS administratorindicator.
Sets the relevant indicators if you want users to receive the following notifications: Notification If Purchase Order Not Opened, Notification If Purchase Order Response Is Missing, Notification If ASN Is Missing, Notification If ConfirmationIs Missing, Notification If Invoice Is Missing,
Do let me know.
Regards
- Atul

Difference between Snapshot scenario and non cumulative scenario

Hi,
Can any one please tell me the difference between snapshot scenario and non cumulative scenario in
inventory management.
Also please give example. I read the pdf " how to handle inventroy management scenarios", but can any one please give some easy to understand examples.
full points guaranteed-

hi,
In Non-cummulative method your stock movements are stored in the cube (inflow and outflow of NC KF) and the Total stock is calculated during query execution. Hence if there are lot of movements in the stock for the period you want to report on, query will take long time to execute.
In case of Snap shot scenario Stock movements are not loaded to cube. you use ODS to load the status of the stock and then from ODS you can load to Cube once in a month. So only summarized data will be availabe in Cube. Reporting will be fast.
Check the below threads
Inventory Management - SnapShot model
snapshot scenario?
SNAP SHOT Scenario in IM

Difference between Classic Scenario and Extended Classic Scenario

Hi Expers,
I need your help again........:-)
I just want to know what is the differne between classic and Extended Classic Scenario.
Points will be rewarded
Thank you
sam

Hi Sam,
(explaination frm a previous thread)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Please check this too:
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
BR,
Disha.

BADI for Classic and Extended Classic Scenario

Hi,
   Please   provide list of Reports and BADI's for
       Classic and Extended Classic Scenario.
Thanks,
Srini

Hi,
In SRM there will be a number of BADI's are Available, We can utilize them according to the requirements
As per the request few important BAID are provided below..
Workflows
1). BBP_CHNG_AGNT_ALLOW:          Allow / Allow Change/Add Approver
This BADI is implemented not to allow users to change the approvers in the workflow.
2). BBP_WFL_SECUR_BADI:          Overwrites the authorization level of the approver
This BADI controls the restart of the workflow
Purchasing Related
1). BBP_PGRP_FIND:               Shopping Cart: Determine Responsible Purchasing Group(s)
This determines the responsible purchasing group for the shopping carts.
Shopping Cart Related
1). BBP_SC_MODIFY_UI:          BADI to Change Shopping Cart Layout
2). BBP_GROUP_LOC_PO:          Exit Grouping of Items for Local Purchase Orders
This splits local PO if more than one contract in a PO.
3). BBP_TARGET_OBJECTS:          Exit while determining target objects in backend
4). BBP_WF_LIST:               Change Worklists and Search Results Lists
This is used to restrict the search results for the user.
5). BBP_CTR_BE_CREATE:          Exit when Creating a Contract in the Backend System
6). BBP_CREATE_PO_BACK:          Exit while creating a purchase order in the backend system
This BADI is used to add the shopping carts attachments to the PO and also to make adjustments in payment terms, currency etcu2026
7). BBP_DOC_CHECK_BADI:     General BAdI in Cross-Check for Message Returns
8). BBP_DOC_CHANGE_BADI:     BAdI for Changing EBP Purchasing Documents
9). BBP_ECS_PO_OUT_BADI:     ECS: PO Transfer to Logistics Backend
Thanks
prasad .s

Order Change Management and direct manufacturing technique (SOBSL 52)

Dear all,
there is a statement in our SAP development team, that I can hardly believe:
Order Change Management and direct manufacturing technique are not fully supported in SAP standard (ECC6.0).
Can any body help me with this issue?
Kind Regards
Bernd

Dear Bernd,
please see SAP note 436928, which descriped the restrictions from OCM.
Regards,
Sabine

HTTP and RFC related scenarios

Hi
Can you give HTTP and RFC related scenario links ?
Urgent pls
Thanks,
Message was edited by:
s s

Hi s s,
see the below links, they will help u.
HTTP to RFC
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci983752,00.html
http://help.sap.com/saphelp_nw04/helpdata/en/f6/e002416225f023e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
Is it possible to use the RFC sender adapter for asynchronous calls? Async call
<a href="http://File to RFC using BPM-Starter Kit: By Arpit Seth">File to RFC using BPM-Starter Kit: By Arpit Seth</a>
regards
sreeni

BTO,BTS,CTO and ETO Manufacturing Scenarios impacting MES or not?????????

Similar Messages

Maybe you are looking for