MRP Type and procurement type tabs in mmd

Hello Experts,
I was trying to check the MRP Type for a material master.
In MM01, I could not locate such a tab. I think I have seen it before.
I have entered most of the selection info like Material code etc.
Or is it that MRP type is not visible from material master?
What if its blank?
I check the MARC table for the material code and the MRP type is blank.
Also, in which tab can I maintain the procurement type? Could not find such a field in mmd.
Have a nice day everyone.
regards
Bass

Hi,
MRP type and Procurement type are under tab MRP 1 & MRP 2 respectively in material master.
Check MRP1/2/3/4 tabs all information you need is there.
Kapil

Similar Messages

Procurement type and procurement indicator

hi all,
There is a mismatch occurred in procurement in PS.
i have configured a procurement indicator in ps and in control data i have checked PReq Network.
After that When i assigned a material to the activity .
In material details under purchase data tab it is showing procurement type as "Third party Requisition for WBS "
and under procurement parameter tab it is showing procurement indicator same as given and procurement type as "Third party Requisition for WBS "
Why this is mismatch or any thing extra we need to configure.
Also i want to create new procuremetn indicator which will create PR for WBS only what setting we have to do for this .
thanks
shiv
Edited by: Shiv on Aug 26, 2008 10:23 AM

Hi Raja,
Back flush indicator can be maintained in many places.....
Material master record (MRP2 view)
Resource (Basic Data screen)
Master recipe (General Data screen for component assignment)
Process order (General Data screen for the material component)
Priority works as mentioned in the below diagram....
Thanks
Kumar

MRP uses special procurement type L for material .ME174

Hi All:
   1 .When I tried to create PO for non-valued material using ME21N,SAP displayed message "MRP uses special procurement type L for material"- .ME174.
    (Non-vaued material is customized material type which has no accouting view and is supplyed by suupplyer for free.)
   2.I checked the material setting in MM03 finding that the Procurement type has been set as 'F' and the Special procurement has been set as '30'.
   3.I checked the SPRO finding that the setting as following path finding that Special procurement has been set as L.
    IMG > MM > Consumption-Based Planning > Master Data > Define Special Procurement Types
   So what other problem is with my setting or configuration for the creating PO?
Thanks.

Hi,
You may want to double check the customization entry for special procurement type 30. Do ensure you are checking for the correct plant and you have "L" maintained against special procurement in the details section.
If this doesn't help, a post in the MM forum - SAP ERP - Logistics Materials Management (SAP MM) could help.
Anoop

CK86_99 and CK86: display purchase group and procurement type

Hi Gurus,
I have a request
Can I insert the purchase group and procurement type in the layout of tcode CK86_99 and CK86 when we have a material item ?
I have seen that we can define the control parameters for the Product Cost Controlling Information System.
Tcode OKN0 but we have only the basic fields and we haven't the specific fields for division.
Thanks in advance
Marco Ferrari

Hello Marco,
I do not think you have any options to change the layout except for the fields that are available in the transaction screen. It is a standard report and is not a one based on report painter layouts. It would be helpful if you can consult an ABAP person who can throw some light or create a report for you.
Kind Regards // Shaubhik

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

Difference between line type and table type

hi,
can any one explain the difference between line type and table type . and how to declare a internal table and work area in BSP's

hi,
Go through this blog, this might help you.
/people/tomas.altman/blog/2004/12/13/sdn-blog-how-to-do-internal-tables-in-bsp
People who have worked with ABAP for a while sometimes forget that the internal table concept is rather different than what exists in most programming languages. It is very powerful, but at the same time can be confusing.
In SAP it is possible to have a table which is the rows and a headerline which is the working area or structure which can then be commited to the table.
With a BSP, if we try to create an internal table within the BSP event or layout we will get the following error: mso-bidi-
                        "InternalTableX" is not an internal table - the "OCCURS n" specification is mso-bidi- missing.
class="MsoNormal"><![if !supportEmptyParas]>The problem we are seeing as an inconsistency has to do with the difference between classic ABAP and ABAP Objects. When SAP introduced ABAP Objects they decided to clean up some of the legacy syntax and create stricter rules. However they didn't want to break the millions of line of code that already existed, so they only implemented these stricter checks when OO is being used. Therefore you can declare a table with a header line in a regular ABAP program or Function Module but you can't have one with a header line in OO.
Because everything in BSP generates ABAP OO classes behind the scenes, you get these same stricter syntax checks. My suggestion is that you have a look in the on-line help at the section on ABAP Objects and always follow the newer syntax rules even when writing classic ABAP programs.
In a BSP when we need to work with a table we must always do the following:
1, in the Types definitions create a structure:
                        types : begin of ts_reclist,
mso-bidi-        style='mso-tab-count:2'>                            receiver type somlreci1-receiver,
mso-bidi-        style='mso-tab-count:2'>                 style='mso-tab-count: 1'>             rec_type type somlreci1-rec_type,
mso-bidi-         style='mso-tab-count:2'>                            end of ts_reclist.
mso-bidi- <![if !supportEmptyParas]> <![endif]>
but we must remember this is only a structure definition and we cannot store anything in it, although we can use it elsewhere as a definition for Structures(WorkAreas)
2, in our Types definitions (this is the best place for this one as we can then access it from many areas without having to create it locally) so in the Types definitions we must create a TableType:
class="MsoNormal">                         types : tt_reclist type table of ts_reclist.
class="MsoNormal"><![if !supportEmptyParas]> <![endif]> this TableType is our table definition and again we cannot store anything in it, but we can use it elsewhere as a definition for InternalTables
3, now that you have laid the foundations you can build and in the event handler, it is now simply a case of creating the InternalTable based upon the Table definition:
                       data: t_reclist type tt_reclist.
and creating the structure based upon the structure definiton:
<![if !supportEmptyParas]>   <![endif]>                         data: s_reclist type ts_reclist.
as described above, the structure becomes the work area and this is where you assign new values for elements of the table eg:<![endif]>
                        s_reclist-receiver = '[email protected]'.   "<-- change address
mso-bidi- <![if !supportEmptyParas]> <![endif]>
mso-bidi-                         s_reclist-rec_type = 'U'.
and then once the data is in the elements of the structure, the structure can be appended to the internal table as follows: class="MsoNormal">
                        append s_reclist to t_reclist.
<![if !supportEmptyParas]> <![endif]>
the internal table will then be readable for the ABAP function and can be applied for example as follows: class="style1">           style='mso-tab-count:1; font-family: "Courier New", Courier, mono;'>
class="style1">CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
                        EXPORTING
style='mso-tab-count:2'>                                    document_data = docdata
style='mso-tab-count:2'>                                    DOCUMENT_TYPE = 'RAW'
style='mso-tab-count:2'>                                    PUT_IN_OUTBOX = 'X'
style='mso-tab-count:2'>                                    COMMIT_WORK = 'X' "used from rel.6.10
                        TABLES
mso-bidi-font-size: style='mso-tab-count:2'>                                    receivers = t_reclist
class="style1"> <![if !supportEmptyParas]>   <![endif]>
<![if !supportEmptyParas]>F inally, a comment from Thomas Jung,
<![if !supportEmptyParas]> when defining my work area for an internal table I like to use the like line of statement. That way if I change the structure of my table type, I know that my work area will still be OK. Second, your types and table types don't have to just be declared in your code. You can create a table type in the data dictionary and use it across multiple programs(also great for method and function parameters). I really push hard for the other developers at my company to use the Data Dictionary Types more and more.
Hope this helps, Do reward.

Diff b/w reference type and elementary type

hi all
can any one what is the diff b/w reference type and elementary type in data element ....
thanks
lokesh

The data type attributes of a data element can be defined by:
Specifying a domain whose attributes are copied by the data element.
Specifying a build-in type where the data type, number of places, and possibly decimal places can be directly specified.
Specifying a reference type, i.e. reference to a class, an interface, a type defined in the Dictionary, a built-in type, or a generic reference to ANY or DATA.
In the maintenance screen you can set the option you require by setting the appropriate flag (domain, built-in type, reference type) and filling in the corresponding input fields.
A reference type is a reference to another type. There are the following kinds of reference types:
Reference to a class or an interface
Reference to a type defined in the Dictionary
Generic reference to ANY, OBJECT, or DATA
Reference to a built-in Dictionary type with specification of the length and possibly also the decimal places
You can use a reference type to define the data type properties for a data element, or for typing the component of a structure or the line type of a table type.
In the field Referenced type, enter the name of a class, an interface, the generic references DATA, OBJECT, ANY, or the name of a type defined in the Dictionary. If the reference type is to be a predefined Dictionary type, choose the reference to the predefined type. Enter the number of characters and, if required, the number of decimal places.
where as
The data class describes the data format at the user interface.
If a table field or structure field or a data element is used in an ABAP program, the data class is converted to a format used by the ABAP processor. When a table is created in the database, the data class of a table field is converted to a corresponding data format of the database system used.
You can find a detailed description of the data classes allowed in the ABAP Dictionary in Overview of the Data Classes.

Automatic determination of Delivery type and Billing type in a sales order

Hi,
I want to know that in a sales order cycle, how does automatic assignment of delivery type and billing type takes place after we create a sales order?
For example,when I create an outbound delivery for a sales order of type normal (OR) then in that case how does the system knows that it has to create an outbound delivery of type LF.How does the system propses it automatically and same is the case of billing document.

Hi
In customising the sales document type (Tcode VOV8) -
specify the default Delivery type in the field DELIVERY TYPE in the 'Shipping' area of the sales document type customisation.
Similarly you can specify the billing type in the BILLING area for both Delivery related billing and Order related billing.
Thanks,
Ravi

How to trigger a form based on object type and process type

Hi all,
I am new into SRM.. I have been asked to develop a form by cloning an existing standard form..
Using bbp_output_change_sf badi you can trigger the form by passing the object type but the scenario is such that depending on the object type and process type the new form should be triggered.
The parameter iv_object_type passes the object type but how could i pass the process type ?
In the badi I noticed an import parameter is_event that has a field called transction_type that carries the process type but this field never got populated when i checked using debugger.
Please help as to how i can trigger the form based on the object_type and the process_type.
Thanx in advance.

Thanx again Jay Yang.. Well is there any possibility that you could get the items that were confirmed..
Let me eleborate..
Suppose in the PO u order an item for 10 nos and 5 gets confirmed and u return 2..
Well in my case it is that i need to fill up a field Qty returned / Qty confirmed..
I was able to get the number of items from the PO by passing the the passing the parameter to the FM "bbp_pd_conf_getdetaill"
but i dont know how to get the number of items been confirmed..
The quantity field in the line item structure gives me the number of items returned..
Can u tell me how to get the number of items been confirmed....

Calling Oracle Stored proc with record type and table Type

I have a oracle SP which takes record type and table Type which are used for order management.
Is there anay way to populate parameters with these datatypes and call the stored procedure using ODP.NET?
Please help.
Thanks in advance

Hi,
ODP supports associative arrays and REF Cursors. There is no support for PLSQL table of records.
Jenny

How does a record type and table type works

Hi,
How a record type and table type work for the ref cursor,
below i m giving an example but its giving me errors
can any one help me for this?
declare
type empcurtyp is ref cursor;
type rectype is record (veid t.emp_id%type, vename t.ename%type);
TYPE tabtype IS TABLE OF rectype;
empcv empcurtyp;
vtab tabtype;
begin
open empcv for select emp_id,ename from t;
loop
fetch empcv into vtab;
exit when empcv%notfound;
dbms_output.put_line(vtab.vename||vtab.veid);
end loop;
close empcv;
end;
here we hav table t and i m taking only two fields of the table t which r emp_id and ename.

Hi,
What errors are you getting with this? From experience you don't need a loop to put the records into the ref cursor its usually done on block.
HTHS
L :-)

Oracle Streams 'ORA-25215: user_data type and queue type do not match'

I am trying replication between two databases (10.2.0.3) using Oracle Streams.
I have followed the instructions at http://www.oracle.com/technology/oramag/oracle/04-nov/o64streams.html
The main steps are:
1. Set up ARCHIVELOG mode.
2. Set up the Streams administrator.
3. Set initialization parameters.
4. Create a database link.
5. Set up source and destination queues.
6. Set up supplemental logging at the source database.
7. Configure the capture process at the source database.
8. Configure the propagation process.
9. Create the destination table.
10. Grant object privileges.
11. Set the instantiation system change number (SCN).
12. Configure the apply process at the destination database.
13. Start the capture and apply processes.
For step 5, I have used the 'set_up_queue' in the 'dbms_strems_adm package'. This procedure creates a queue table and an associated queue.
The problem is that, in the propagation process, I get this error:
'ORA-25215: user_data type and queue type do not match'
I have checked it, and the queue table and its associated queue are created as shown:
sys.dbms_aqadm.create_queue_table (
queue_table => 'CAPTURE_SFQTAB'
, queue_payload_type => 'SYS.ANYDATA'
, sort_list => ''
, COMMENT => ''
, multiple_consumers => TRUE
, message_grouping => DBMS_AQADM.TRANSACTIONAL
, storage_clause => 'TABLESPACE STREAMSTS LOGGING'
, compatible => '8.1'
, primary_instance => '0'
, secondary_instance => '0');
sys.dbms_aqadm.create_queue(
queue_name => 'CAPTURE_SFQ'
, queue_table => 'CAPTURE_SFQTAB'
, queue_type => sys.dbms_aqadm.NORMAL_QUEUE
, max_retries => '5'
, retry_delay => '0'
, retention_time => '0'
, COMMENT => '');
The capture process is 'capturing changes' but it seems that these changes cannot be enqueued into the capture queue because the data type is not correct.
As far as I know, 'sys.anydata' payload type and 'normal_queue' type are the right parameters to get a successful configuration.
I would be really grateful for any idea!

Hi
You need to run a VERIFY to make sure that the queues are compatible. At least on my 10.2.0.3/4 I need to do it.
DECLARE
rc BINARY_INTEGER;
BEGIN
DBMS_AQADM.VERIFY_QUEUE_TYPES(
src_queue_name => 'np_out_onlinex',
dest_queue_name => 'np_out_onlinex',
rc => rc, , destination => 'scnp.pfa.dk',
transformation => 'TransformDim2JMS_001x');
DBMS_OUTPUT.PUT_LINE('Compatible: '||rc);
If you dont have transformations and/or a remote destination - then delete those params.
Check the table: SYS.AQ$_MESSAGE_TYPES there you can see what are verified or not
regards
Mette

Idoc types and message types

Hi ,
Anyone can send what are all the std idoc types and message types are there in SAP?
Coz i dnt have SAP.
Please let me know

The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
An IDoc type consists of the following components:
·       a control record
This is identical for each IDoc type.
·       several data records
One data record consists of a fixed key part and a variable data part. The data part is interpreted using segments, which differ depending on the IDoc type selected.
·       several status records
These are identical for each IDoc type and describe the statuses an IDoc has already passed through or the status an IDoc has attained.
You find various IDOC / Message types in SAP -
http://www.erpgenie.com/sapedi/message_types_masterdata.htm
IDoc Types - Message Types -Accounting Business Processes
IDoc Types - Message Types - HR Business Processes
IDoc Types - Message Types - Logistics Business Processes
Eg.
General       Message types / IDoc types / BAPI
Vendor        CREMAS / CREMAS02
Customer      DEBMAS / DEBMAS03
Accounting   Message types / IDoc types / BAPI
G/L account   GLMAST / GLMAST01
Cost center     COSMAS / COSMAS01
Cost element COELEM / COELEM01

Confusion on pair type and Processing Type

Dear Experts
I have the the below doubt in TIP Table
Pair type gives the information on the how the Time pairs being generated as
0-      Non recorded Time
1-      Attendences
2-      Absences
3-      Attendences Recorded from client
Processing Types also gives information on how the Time pairs are coming with below spec
- Pair is deleted at a later stage
BLANK Pair not included in calculation of productive time
P Attendance pair, included in calculation
of planned working time
A Absence pair, included in calculation
of planned working pair
S Planned working time pir
M Overtime pair
Kindly let me know on what senerios we go with pair type and processing type as they have the same meaning
Regards
Giri

Hi Shruit
i am clear but as mentioned in pair type 1= attendence (2011 - Positive) and Planned working time for negative . in processing type S, A,P also signifies the information how the Time pairs are Generated   and also we have Origin indicator of time pair O which specifies wheather the time pairs are coming from E,M.A,P and D.
Since they have same information why Sap has defined pair Type processing Type and Origin Indicator
                                                             I got the inputs theriotically but practically i am not able to get the TIP Table to read and understand .
Thank you very much for the inputs
Giri

Is there any standard ODS for Contract (value type and quantity type)?

We know that in MM, contract records can be categorized into two different categories, Value type and Quantiy type. We are trying to see if there is any Contract ODS in business content that we can install which can take care of these two types of contract records that we can bring them over to BW from R3?
Thanks

Hi Kevin,
Please see this link,ODS looks related to your requirement.But seems its for CRM and not for MM.
http://help.sap.com/saphelp_nw04/helpdata/en/38/c3813ed9d23e44e10000000a114084/frameset.htm
cheers,
Vishvesh

MRP Type and procurement type tabs in mmd

Similar Messages

Maybe you are looking for