Flow and customizing process of st.grp 11

Hi Guru,
As per my client requrimet they want to implement st grp 11,but i dont what are setting done for that.
Pl let me know for customization purpose how can do the planning using this scenario give detail flow of this st grp along with
business case. what are customization setting for st grp 11 what type result show in system ?
With Regards,
Ravindra.

Master data setting:
in MRP 3 view maintain Strategy 11 and Mixed MRP as gross requirement.
Process Sequence:
Create a PIR in MD61( system will take reqmt type BSF- for strategy 11)
and do the normal production process,
PIR will be reduced, when you do the GR for the production order.
business case: in cement Industry / steel Industry - The production will be continuous eventhough If you have enough stock, the production department won't bother about the inventory In ware house, strategy 11 - won't consider warehouse stock during MRP run

Similar Messages

Difference between java page flow and java process definition

I have joined a BEA WebLogic Integration project as an entry level BEA developer. I have a big question on the real difference between a jpf and a jpd. My co-workers say there is actually no difference, but I don't believe so. I think a jpd is more like a back-end process and it may or may not not need a View(MVC). While a jpf is the Controller(MVC) and is closely related to a web-based application where all the navigation logic(and only navigation logic) resides. A jpf normally should have a View(rendered on browser or other terminals) to present data from Model. I strongly believe this is true. But my project manager and my team lead, both are very technical guys, fiercely object to my understanding. I am extremely curious to have input from the BEA community on this fundamental concept.

I find it hard to believe your team lead really believes there is no difference between a JPF and a JPD. There are numerous differences, both conceptually and technically.
I believe your understanding of the differing roles of the two is correct. A JPF would represent the view of an application, and a JPD would represent callable services of an application, and server-side business logic.
From the technical point of view, a JPF, assuming it avoided certain features, can be deployed on Tomcat. The core of it is a pure servlet application. A JPD is an EJB, either a SLSB or a SFSB.

Creating variables in Process Flows and using thse variables in the filter

Hi,
I am new to OWB and in learing stage. Need to information.
*1. as to how pass/create/use variables to OWB mapping ?*
*2. Creating variables in Process Flows and using thse variables in the filter operator of the OWB mapping?*
*3. Other mechanisms of how to create/use variables within OWB mapping itself ?*
can you please provide the above details and guide me / help me in this regard.
Thanks,
skms.

1. Add parameters to your mapping using the MAPPING INPUT PARAMETER from the pallette.
2. Add parameters to the START operator in the process flow. Bind the process flow parameter to the Mapping parameter.
3. May be appropriate to use CONSTANTS instead of parameters.
Regards
Si

Sto process find vendor and customer

we are Creating STO with ME27 tcode from one plant to another plant ie from A120 to S122.
Already the configurations are done by someone.
Now i took the purchase order xxxxx and open in me23n.
As per the process we need to Assign vendor to Delivering plant
ie XK03 >Purchasing view>Extras>Add. Purchasing data>Plant
I have the supplying plant and want to find the vendor to which it was
assigned. I searched the ME23n Tcode and not found the vendor(envirnoment-vendor).
I checked in lfa1 table also to some extent, but not found.
And also tell me how to find the plant in cusotmer.

Thank you all .
Chakrapani it means that some of the following settings are not required for sto ie plant to plant within same company code?Could you please tell which are not required?
1.Create a vendor for the company code of receiving plant: T-Code XK01.
2 Assign this vendor to Delivering plant
Go to XK02 >Purchasing view>Extras>Add. Purchasing data>Plant
3. Create internal customer with the sales area of the vendor. Go To XD01
4.In Pricing procedure determination relevant to STO, assign document Pricing Procedure and customer pricing procedure appropriate for STO to get the pricing in the invoice.
5.Maintain condition records for the relevant pricing condition.
6. Some more setting for STO: Go to MM> Purchasing > Purchase Order > Set up STO> define shipping data for plants > Go to Receiving plant >assign customer here & Supplying SA (for billing) to Receiving plant here
7. Go to MM> Purchasing > Purchase Order > Set up STO> define shipping data for plants > Go to Supplying plant and assign the sales area of receiving plant.
8. Go to MM> Purchasing > Purchase Order > Set up STO> assign delivery Type & Checking rule
Assign the delivery type to document type. In this case, Delivery type NLCC is assigned to Document type NB
9. Go to MM> Purchasing > Purchase Order > Set up STO>Assign document Type, One step Procedure, Under delivery tolerance
Assign the document type NB to supplying plant and receiving plant
10. After all settings , Create the STO using T-Code:ME21N and Save.
11. Create Delivery :VL10G
Click on the Background Button after selecting line item
A message is flashed : See log for information> next Click on Log for delivery creation Button >click on line item>click on document button to get Delivery document No
12. Picking, PGI:VL02N
13. Billing:VF01N
Note:
1)Sales View is maintened for Material in both plant
2) Loading group is maintained for that material in the sales org/ Gen Plant view
3) Material is extended in both plant
4)In T.code:OVL2 ,,,,,, maintain the Shipping condition, loading group, Plant & Primary shipping point combination. The loading group should be equal to the Material master loading group & shipping condition equal to customer shipping condition.

Custom process code and FM for custom IDoc...

Hello Experts,
I created a custom IDoc based from ARTMAS05 IDoc. This is because we only need 3 segments and
the standard idoc(Artmas05) contains so many segments that we need.
Now, will I create a custom process code and FM for this? how do I go about this?
Thank you guys and take care!

Hello,
Here are the Steps that we need to be following while creating a Custom Process Code with Custom Function Module. ( Since the Segments to be handled are very Less, I am recommending that you go for a Custom Function Module).
1. Go to SE37 Create a Function Module. Please ensure to Create it with the IMPORT / EXPORT /TABLES parameters exactly in the way that they exist in any Standard SAP Inbound FM (Refer to IDOC_INPUT_ORDERS for example).
2. Once our FM is Ready (Need not be Complete with the Code to go ahead with the Process Code Creation) and Active, the next Step is to Create an Entry in the Transaction Code BD51 where we will register the Function Module.
3. Next, we'll have to go to T-Code WE57 where we'll have to make an entry for the Function Module with the IDoc Type & Message Type.
4. Finally, go to WE42 and Create a New Process Code and assign the Function Module and the Message Type.
NOTE 1 : The Process Code is, as we know, Client Dependent. So, once you create a Process Code, we need to have it migrated to the Testing Environment to Start & Carry Out Testing.
NOTE 2: If Step 2 & 3 are missing, then we'll not be able to assign the Function Module in WE42 while Creating Process Code.
Hope it was helpful.
Thanks and Regards,
Venkata Phani Prasad K

Process flow for customer services

Hi ,
I want to know the process flow for customer services.Means when customer return the product for repair or replacement,then how we run the complete process in system.What is the various tcode for this process.
Please ASAP
Regards
Prabudh

Have a look at this [link|http://help.sap.com/saphelp_crm40/helpdata/en/b0/87e20ee4f20148acc496c5525f4399/content.htm] if it for any help. couldn't find anything better
Regards

Block Planning High level process flow and configuration - PPDS

Dear Experts,
I am trying to understand more about Block planning
from my understanding
Block Planning is a pre-assignment of resource and capacities for a limited duration of time which mean dedicated resource for a particular operation
correct me if i am wrong
which mean I am able to hold a Resource A for a particular date like say march 20 and march 21 for a particular production version of operation like say 10
if my understanding is correct what are the basic configuration setting and the process flow
I am sure you need to explain loads , i am sorry about that
Thanks in advance
Regards
Raj

Hello,
Finally we found a partial solution to work with Adjust & Reschedule Block limits.
The overloaded blocks are extended inside to the cycle limits. Unfortunately the blocks with free capacity are not shortened.
Does anybody have an idea why the heuristic is working for the extend but not for the shortened?
Thanks, Marius

Business Flows for Sales and Contracts process

Hi,
I needs Business Flows for sales and contracts process for my project.
Does anybody knows where i can find these BFA ?
Thanks
Regards
Mehdi

Hi mehdi;
Please check below and see its helpful:
R12 Responsibilities And Roles Based On Business Flows [ID 406401.1]
Regard
Helios

Tools for running process flows and mappings

The operations/production area is responsible for running process flows and mappings in a day by day base. As developer, I need to implement a solution that allow them run these artifacts. For this purpose, is there any tool apart from Control Center ????
Thnks

The scripts you mentioned (sqlplus_exec_background_template.sql and sqlplus_exec_template.sql) can be used for command line execution of mappings.
We do not run these in Oracle Workflow, as we already have an enterprise scheduling platform, Redwood Cronacle in our case. (Also one finds AppWorx and others in this area, see e.g. http://www.bmc.com/USA/Corporate/attachments/BMC_Article2.pdf)
Regards, Erik Ykema

Documentation of data flow and processes in BW

Hi,
Is anyone aware of the possibility to document data flow and job-flows from BW (source systems, datasources etc all the way to queries) and export it from BW.
I am looking for a SAP certified tool like ie. Erwin that can collect this documentation from BW. I have not been able to find out if Erwin supports BW.
My hope is that - now that these things are done in BW - I can extract/export this documentation and use it in our general documentation environment.
The alternative is to manually document it.
Regards,
Mick
Denmark

Hi Mick,
I don't think that there is a tool like the one you are talking about...
however, if you select your infoprovider and then right-click->display data flow...in this way, you can obtain a picture of your data flow from the datasource to your provider with all the interdependencies !
Hope it helps !
Bye,
Roberto

Impacts in COPA of changing material and customer master data

Dear experts,
In my company we are considering following scenario:
Currently mySAPerp 6.0 is implemented for all modules for the mother company.
We have developed a new global template where there are significant changes versus the existing system, especially in the SD processes. Material and customer master also change significantly in terms of content in the tables/fields and/or values in the fields.
The idea was to build the template from scratch in a new machine and roll-out all group affiliates, but now we are considering the possibility of making an evolutionary of the current system and try to stretch it to the processes defined in the global template.
The scenario we want to analyze is: Keeping same organizational structure in terms of Company code, CO area and Operating Concern in existing SAP client and make an evolutionary of the existing settings to the global template processes.
The doubts we are having are the following:
Changing material & customer master data: Impact in COPA
Option 1: Material master data and customer master data codes are maintained but content in the tables/fields is changed substantially, both in terms of logical content of specific fields and/or the values in the specific fields. We have following examples of changes.
Case 1: source field in material master changes logical content. E.g. Material master field MVGR1 is currently used for product series (design line) and the content changes to be the Market Segment. The product series will be moved to a classification field. At least 5 other fields are affected by this. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 2: the source field is not changed so that the logical content of the field remains but the values change, i.e. for the same concept there will be different codifications. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 3: Characteristics where currently the source material master field is a Z field and the derivation is via table look up and where the Z field changes to a classification field. How can you convert the existing COPA line items to ensure that attributes are aligned? Should new characteristics be created or just change the derivation logic of the characteristic?
Option 2: Material master data and customer data codes are re-created (codification of records is changed), meaning that new material and customer codes will exist and content in tables/fields is changed (as in option 1)
Case: material and customer codes are changed. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Iu2019ve never phased a similar scenario and I fear that maintaining operating concern while changing source master data and also SD flows (we have new billing types, item categories, sales doc. Types, order reasons) may lead to inconsistencies and problems in COPA.
I would like to ask you experts if you have come across a similar scenario and if from your experience, it is something feasible to do or there are many risks involved. What can be the impact of this scenario in existing Operating Concern for both option 1 and 2 and what would be the key activities to perform to adapt the existing operating concern. What will be the impact of the needed conversions on P&L reporting?
Sorry for the long story. I hope you can help me out.
Thanks and Regards,
Eric

Hi,
First i think you will need to test if it works for new COPA documents created via billing.
If it works fine then the issue is if you wish to apply these changes to the historical data already posted.
Normally there are transactions like KE4S where you can repost the billing document to COPA
However this may not be viable for bulk postings
You can perform realignment (KEND) but this only works at the PA segment level (table CE4XXXX)
regards
Waman

Flow of reversal process

Hi experts,
I have sold finished goods to customer , where customer checks the goods and found some of the things may wrong and he returning the the failed goods. How I have to get this by using SAP and what is the flow and t-codes.
Thanks.

Return material from customer:
You need to receipt the rejected goods through SD Module (VA01 - Sales Order type RE).
The steps are as follows :
1. Create a return request. (Using Sales Order in SD)
2. Create outbound delivery according to return request.
3. If the setting is correct in the outbound delivery screen SAP will automatically switch post goods issue button into post goods receipt. The setting is in sales order item category and delivery type.
4. In the standard system the movement type used is 651.
5. After post goods issues receipt is done using outbound delivery, the quantity is placed in blocked stock without value updating.
6. You will then decide if the return quantity are indeed bad stock or not.
7. Transfer Posting from block stock to unrestricted stock (mvt type 453), this will have accounting effect (Debit Inventory, Credit COGS)
8. Goods Issue to scrap account how to create new titles which can be used in creating the "address" view on the Vendor master.{T-Code: XK01}
In config go to Basis Components --> basis services --> Address Management --> Maintain title texts
Return Sales Order Flow Transaction:
Process 1:
A. Create Return Order (with or without reference to preceeding document): VA01 / VA02 / VA03
B. Create Return Delivery & Post Goods Receipt: VL01N / VL02N / VL03N
Process 2:
A. Change Return Delivery (Remove Billing Block): VA02
B. Create Credit Memo: VF01 / VF02 / VF03
Regards,
Rajesh Banka

Flow and FlowN equivalent activities in OSB

What are the equivalent acivities for Flow and FlowN of BPEL in OSB ?
In other way , what are the activities available in OSB for performing parallel processing of tasks a. when number of paralle branches are static b. When they are dynamic.

Got this from Oracle Documentation !
http://docs.oracle.com/cd/E23943_01/dev.1111/e15866/tasks.htm#OSBDV204
There are two Split-Join patterns, the Static Split-Join and the Dynamic Split Join.
The Static Split-Join can be used to create a fixed number of message requests (as opposed to an unknown number). For instance, a customer places an order for a cable package that includes three separate services: internet service, TV service, and telephone service. In the Static use case, you could execute all three requests in separate parallel branches to improve performance time over the standard sequential execution.
The Dynamic Split-Join can be used to create a variable number of message requests. For instance, a retailer places a batch order containing a variable number of individual purchase orders. In the Dynamic use case, you could parse the batch order and create a separate message request for each purchase. Like the Static use case, these messages can then be executed in parallel for improved performance.
Marking the thread as Answered. !

Mm flow and SD flow

Hi,
Cna any body explain what is mm flow and sd flow

HI,
<b>
SALES & DISTRIBUTION MODULE RELATED TABLES:</b>
Cycle:
Enquiry->Quotation->Sales Order->Delivery(Picking, Packing, Post Goods
Issue and Shipment)->Billing-> Data to FI
TABLES and Important Fields:
VBAK: Sales Document(Header Data) (VBELN)
VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)
Enquiry, Quotation, Sales Order are differentiated based on Doc.
Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,
for Quotation 'B' & for Order it is 'C'.)
LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)
LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)
(LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)
VTTK: Shipment Table (Header Data)(TKNUM)
VTTP: Shipment Table (Item Data)( TKNUM,TPNUM,VBELN)
(VTTP-VBELN = LIKP-VBELN)
VTFA: Shipping Document Flow(TKNUM,VBELV,VBELN)
VTPA: Shipping Partners data(VBELN,PARVW,KUNNR,PERNR)
VTTS: Stages in Shipment(TKNUM,TSNUM,TSTYP)
VTSP: Transport Stage/Shipment Item Allocation(TKNUM,TSNUM,TPNUM)
VEKP: Handling Unit: Header(Packing)(VENUM,VSTEL)
VEPO: Handling Unit: Item (Packing)(VENUM,VEPOS,VBELN)
VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)
VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)
(VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)
Apart from these tables there are lot of other tables which starts with
V, but we use the following tables frequently.
VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)
VBTYP= C(Sales Order) VBTYP=J(Delivery) VBTYP=M(Invoice)
VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)
VBEP: Sales Doc. Schedule Lines Data(VBELN,POSNR,EDATU,WMENG)
VBKD: To get sales related Business data like Payment terms etc.(VBELN,ZTERM)
VBFA: sales document flow data(VBELV,VBELN,POSNV,VBTYP)
VBPA: Partner functions Data(VBELN,PARVW,KUNNR,LIFNR)
VEDA: Contract Data(VBELN,VPOSN)
VEDAPO: Contract Data(VBELN,VPOSN)
KONA: Rebate Agreements (KNUMA,VKORG,VTWEG,SPART)
VBRL: SD Document: Invoice List(VBELN,POSNR,VBELN_VF,NETWR,KUNAG)
VKDFS: SD Index: Billing Indicator(FKTYP,VBELN,FKART,VKORG)
VBSK: Collective Processing for a Sales Document Header(SAMMG,SMART)
VBSS: Collective Processing: Sales Documents(SAMMG,VBELN,SORTF)
VRKPA: Sales Index: Bills by Partner Functions(VBELN,BELNR,KUNDE,PARVW)
VRPMA: SD Index: Billing Items per Material(MATNR,VBELN,BELNR,KUNNR)
TVLKT: Delivery Type: Texts(LFART,VTEXT)
KNA1: Customer Master-General(KUNNR,NAME1,LAND1)
KNB1: Customer Master(Company Code)(KUNNR,BUKRS,PERNR)
KNC1: Customer Master Data (Transaction Figures)(KUNNR,BUKRS,GJAHR)
KNVK: Customer Master Contact Partner(PARNR,KUNNR,NAME1)
KNVV: Customer Master sales data(KUNNR,VKORG,VTWEG,KDGRP)
KNBK: Customer Bank Details(KUNNR,BANKS,BANKL,BANKN)
KNVH: Customer Hierarchy (HITYP,KUNNR,VKORG,VTWEG,SPART)
KNVP: Customer Master Partner Functions(KUNNR,PARVW,KUNN2)
KNVS: Customer Shipment data(KUNNR,VSTEL,TRANS)
KNVI: Customer Tax data(KUNNR,ALAND,TATYP)
LFA1: Vendor Master-General (LIFNR,NAME1,ORT01)
LFB1: Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)
LFC1: Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)
MARA: Material Master-General (MATNR,MTART,MATKL)
MARC: Material Master-Plant data(MATNR,WERKS,EKGRP)
MARD: Material Master- St.Location Data(MATNR,WERKS,LGORT,LABST)
EBEW: Sales Order Stock Valuation(MATNR,VBELN,BWKEY,BWTAR)
TVKO: Sales Organizations(VKORG)
TVTW: Distribution Channel(VTWEG)
TSPA: Divisions(SPART)
TVKOV: Distribution Channels for S.Orgn(VKORG,VTWEG)
TVKOS: Divisions for S.Orgn(VKORG,SPART)
TVTA: Sales Areas(VKORG,VTWEG,SPART)
TVBUR: Sales Offices(VKBUR,ADRNR)
TVKBT: Sales Office Texts(VKBUR,SPRAS,BEZEI)
TVKBZ: Sales Office Assign.to Sales Area(VKORG,VTWEG,VKBUR)
TVKGR: Sales Group(VKGRP)
TVGRT: Sales Group Texts(VKGRP,SPRAS,BEZEI)
TVBVK: Sales Group to Sales office(VKBUR,VKGRP)
TVKWZ: Plants Assign.to S.Orgn(WERKS,VKORG)
T171T: Sales District Texts(BZIRK,BZTXT,SPRAS)
TVLA: Loading Points(LSTEL)
TVST: Shipping Points (VSTEL)
TVSWZ: Shipping Point to Plant(VSTEL,WERKS)
TVPT: Item Categories (PSTYV)
TINC: Customer Incoterms(INCO1)
T077D: Customer Account Group (KTOKD)
T001W: Plants (WERKS)
T001L: Storage Locations (LGORT)
T499S: Locations(WERKS,STAND,KTEXT)
TWLAD: To get address of Storage Location and Plant(LGORT,ADRNR)
TVAK: Sales Document (Order) Types (AUART)
TVAU: Sales Documents: Order Reasons (AUGRU)
TVFK: Billing Document Types (FKART)
TVLK: Delivery Types(LFART)
TVSB: Shipping Conditions (VSBED)
TTDS: Transportation Points(TPLST)
TVKT: Account Assignment Groups (KTGRD)
KONV: Condition Types pricing)(KNUMV,KSCHL,KWETR)
ADRC: To get Addresses of Partners(ADDRNUMBER,NAME1)
VBBE: Sales Requirements: Individual records(VBELN,POSNR,MATNR)
VBBS: Sales Requirement totals Record(MATNR,WERKS,LGORT,CHARG)
VBKA: Sales Activities Data(VBELN,KTAAR)
VBPV: Sales Document Product Proposal(VTWEG,MATNR,KUNNR,CHARG)
T682: Access Sequences (KOZGF)
T682T: Access Sequence Texts (KOZGF,VTXTM)
T683: Pricing Procedures (KALSM)
T683T: Pricing Procedures Texts(KALSM,KAPPL,SPRAS,VTEXT)
T685: Pricing Condition Types (KSCHL)
T685T: Condition Type Texts(KSCHL,SPRAS,KAPPL,VTEXT)
KONH: Conditions (Header)(KNUMH,KAPPL,KSCHL)
KONP: Conditions (Item)(KNUMH,KOPOS,KAPPL,KSCHL)
KONV: Conditions (Transaction Data)(KNUMV,KSCHL,KBERT,KWERT)
KOND: Conditions (KNUMD,ZUSKO,KSCHL)
<b>
MATERIAL MANAGEMENT MODULE:</b>
Cycle:
Purchase Requisition->Request for Quotation(RFQ)->(Vendor Evaluation)->Purchase Order(PO)->Goods Receipt Note(GRN)->Invoice Verification->Data to FI
TABLES and Important Fields:
LFA1--Vendor Master-General (LIFNR,NAME1,ORT01)
LFB1--Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)
LFC1--Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)
LFM1-Pur.Orgn. Related Vendor Data (LIFNR,EKORG)
MARA--Material Master-General (MATNR,MTART,MATKL)
MARC--Material Master-Plant data(MATNR,WERKS,EKGRP)
MARD--Material Master- St.Location Data(MATNR,WERKS,LGORT,LABST)
MAKT--Material Descriptions(MATNR,MATKL,MAKTX)
MBEW--Material Valuation Data(MATNR,BWTAR)
MVKE-Material Master: Sales related Data(MATNR,VKORG,VTWEG)
MDKP--MRP related data(Header)(DTART,MATNR,PLWRK,PLSCN)
MDTB-MRP Table(DTNAM,DTPOS,PLANR)
MCHA--Batches (MATNR,WERKS,CHARG)
MCHB-Batch Stocks(MATNR,WERKS,LGORT,CHARG)
EBAN-- Pur.Reqn. Data (BANFN,BNFPO,BADAT,MATNR)
EBKN-- Purchase Requisition Account Assignment(BANFN,BNFPO,VBELN)
EINA- Purchase Info.Record (General Data)(INFNR,MATNR,LIFNR)
EINE-- Purchase Info.Record (Pur.Orgn Data )(INFNR,EKORG)
ELBK-- Vendor Evaluation Header Data(LIFNR,EKORG,KLASS)
ELBM-- Vendor Evaluation: Material-Related Item(LIFNR,MATNR,EKORG,INFNR,HKRIT)
ELBP- Main Criteria for Vendor Evaluation (LIFNR,EKORG,HKRIT)
EKKO-- Purchase Order Data (Header)(EBELN,BSTYP,BSART)
EKPO-- Purchase Order Data (Item)(EBELN,EBELP,MATNR)
RFQ and PO are differentiated by Doc Type(BSTYP)in EKKO table.
For RFQ it is A and for PO it is F.
MKPF-- GRN Data (Header) (EBELN,BLDAT,BUDAT,XBLNR,BKTXT)
MSEG-- GRN Data (Item)(MBLNR,BWART,LIFNR,MATNR,EBELN)
Apart from this there are lot of tables which begin with 'M'& 'E', but we
use the following very often.
EQUK--Quota(header) (QUNUM,MATNR)
EQUP-Quota(item) (QUNUM,QUPOS,LIFNR)
ESLH--Service Package Header Data (PACKNO,EBELN,VBELN)
ESLL--Lines of Service Package (PACKNO)
ESUH--Ext. Services Management: Unpl.Service Limits: Header Data(PACKNO)
ESKN--Account Assignment in Service Package(PACKNO)
EKKN--Account Assignment in Purchasing Document(EBELN,EBELP,VBELN)
EKBE--PO History Data (EBELN,EBELP,BELNR,BLDAT,MATNR,VGABE)
EKBZ--PO History with delivery Costs(EBELN,BELNR,LIFNR,XBLNR)
EKET--Schedule lines data of a PO (EBELN,EINDT,SLFDT)
EKES--Vendor Confirmations Data(EBELN,EBTYP,EINDT,XBLNR)
T001W-- Plants (WERKS)
T001L-- Storage Locations (LGORT)
T300- Warehouse Numbers(LGNUM)
T301- Storage Types(LGNUM,LGTYP)
T320- Assign. Stor.Locn to WM Warehouse(WERKS,LGORT,LGNUM)
T163F--Confirmation Texts(EBTYP,EBTXT)
T156-- Movement Types(BWART)
T024-- Purchasing Groups(EKGRP,EKNAM)
T024E--Purchase Organizations(EKORG,BUKRS)
T024W--Plants Assign.to P.Orgn(WERKS,EKORG)
T161-- Purchasing Document Types(BSTYP,BSART)
T163-- Item Categorys in Purchasing Documents(PSTYP)
T149D--Valuation Types(BWTAR)
T134-- Material Types(MTART)
T179- Material Product Hierarchies(PRODH)
T179T-Material Product Hierarchies: Texts(PRODH,SPRAS,VTEXT)
TJ02T-System status texts(ISTAT,SPRAS,TXT30)
STKO-- BOM(Bill of Material)(Header)( STLTY,STLNR,STLAL)
STPO- BOM(Bill of Material)(Item)( STLTY,STLNR,STLKN,STPOZ)
STPU-- BOM Sub-Item (STLTY,STLNR,STLKN)
STPN-- BOM Follow-Up Control (STLTY,STLNR,MATNR)
STST-- Standard BOM Link (STOBJ,STLNR,STLAN,STLAL)
STZU- Permanent BOM data( STLTY,STLNR,STLAN,ALTST)
RKPF-- Document Header: Reservation(RSNUM,BWART,ANLN1,KOSTL)
RBKP-- Document Header: Invoice Receipt(BELNR,BLART,GJAHR,BUDAT)
RSEG-- Document Item: Incoming Invoice(BELNR,BUZEI,EBELN,MATNR)
rgds,
bharat.

Create a dummy workbench and customizing object as critical object

Hi!
I am testing now the transport settings for critical objects.
what is the easiest way to create a dummy workbench and customizing object, assign them to transport request and try to transport?
(e.g. Work Bench object: LIMU, DOCU, "Documentation")
Thank you very much!
regards
Thom

I think i misinterpret my requirement.
I have various other applications looking into my metadirectory. There is integration between OIM and Metadirectory and we have to update the various priviledges (multi value data) in Meta Resource form for this so that from MetaDirectory they can flow to other systems. For that i was thinking of using dummy resource object for each resource (attached to Meta). To update the various priviledges (group names and other entitlements) in meta collectively , i think we attached the dummy resource to access policies and once the values will update in dummy resource process form we can update the Meta Process Form accordingly (though i am not sure with this part that how can i achieve this). Also can we define the multi value data field in process form. By default child table having lookup is multivalue field (may be its only my conception) can we add it in core process form?
Pardon me for confusion but i am really patch up between business and technical people requirement :(...
just a follow up i need a pre-populate kind of functionality managing by access policy but after the value pre-populate in dummy resource object process form how to update the value in other process form and update the target resource.
Edited by: user10781632 on Jun 19, 2009 7:05 AM

Flow and customizing process of st.grp 11

Similar Messages

Maybe you are looking for