Material Master Idoc

[Former Member]

Hi ,

Our customer wants an IDoc , which can be send material master data ,I want to learn how can I do this step by step , BD10 is not adequate for me because I want to create change pointer . Can you please help me ?

First I created a message type and assign it to the idoc type and I will create partner, but missing part is how can send material master with standard Idoc by using change pointers ???

Edited by: carlos eduardo on Jan 9, 2008 9:13 AM

[Former Member]

hi Carlos,

REPORT zmm_mat_master_non_stock

NO STANDARD PAGE HEADING

LINE-SIZE 255.

• Standard Include for Selection Screen

INCLUDE bdcrecx1.

• Internal Table for Upload Data

DATA: BEGIN OF i_mat OCCURS 0,

• mbrsh(001), " Industry Sector

• mtart(004), " Material Type

• Views

• Organization Levels

• werks(004), " Plant

• Basic Data1 View

maktx(040), " Material Description

• meins(003), " Unit of Measure

matkl(009), " Material Group

• MTPOS_MARA(004), " Gen Item Category

• Purchasing

ekgrp(003), " Purchasing Group

END OF i_mat.

• Data Variables & Constants

CONSTANTS : c_x VALUE 'X'. " Flag

• Parameters

PARAMETERS: p_file LIKE ibipparms-path. " Filename

• At selection-screen on Value Request for file Name

AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.

• Get the F4 Values for the File

CALL FUNCTION 'F4_FILENAME'

EXPORTING

program_name = syst-cprog

dynpro_number = syst-dynnr

IMPORTING

file_name = p_file.

• Start of Selection

START-OF-SELECTION.

• Open the BDC Session

PERFORM open_group.

• Upload the File into internal Table

CALL FUNCTION 'UPLOAD'

EXPORTING

filename = p_file

filetype = 'DAT'

TABLES

data_tab = i_mat

EXCEPTIONS

conversion_error = 1

invalid_table_width = 2

invalid_type = 3

no_batch = 4

unknown_error = 5

gui_refuse_filetransfer = 6

OTHERS = 7.

IF sy-subrc <> 0.

• MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

• WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

• Upload the Data from Internal Table

LOOP AT i_mat.

• Basic Screen

PERFORM bdc_dynpro USING 'SAPLMGMM' '0060'.

PERFORM bdc_field USING 'BDC_CURSOR'

'RMMG1-MATNR'.

PERFORM bdc_field USING 'BDC_OKCODE'

'/00'.

PERFORM bdc_field USING 'RMMG1-MBRSH'

'C'."i_mat-mbrsh.

PERFORM bdc_field USING 'RMMG1-MTART'

'NLAG'."i_mat-mtart.

• Views Selection

PERFORM bdc_dynpro USING 'SAPLMGMM' '0070'.

PERFORM bdc_field USING 'BDC_CURSOR'

'MSICHTAUSW-DYTXT(08)'.

PERFORM bdc_field USING 'BDC_OKCODE'

'=ENTR'.

PERFORM bdc_field USING 'MSICHTAUSW-KZSEL(01)'

c_x."i_mat-kzsel_01.

PERFORM bdc_field USING 'MSICHTAUSW-KZSEL(02)'

c_x."i_mat-kzsel_02.

PERFORM bdc_field USING 'MSICHTAUSW-KZSEL(08)'

c_x."i_mat-kzsel_08.

• Organization Levels

PERFORM bdc_dynpro USING 'SAPLMGMM' '0080'.

PERFORM bdc_field USING 'BDC_CURSOR'

'RMMG1-WERKS'.

PERFORM bdc_field USING 'BDC_OKCODE'

'=ENTR'.

PERFORM bdc_field USING 'RMMG1-WERKS'

'2000'."i_mat-werks.

• Basic data1 View

PERFORM bdc_dynpro USING 'SAPLMGMM' '4004'.

PERFORM bdc_field USING 'BDC_OKCODE'

'/00'.

PERFORM bdc_field USING 'MAKT-MAKTX'

i_mat-maktx.

PERFORM bdc_field USING 'BDC_CURSOR'

'MARA-MTPOS_MARA'.

PERFORM bdc_field USING 'MARA-MEINS'

'EA'."i_mat-meins.

PERFORM bdc_field USING 'MARA-MATKL'

i_mat-matkl.

PERFORM bdc_field USING 'MARA-MTPOS_MARA'

'NLAG'."i_mat-mtpos_mara.

• Basic data2 View

PERFORM bdc_dynpro USING 'SAPLMGMM' '4004'.

PERFORM bdc_field USING 'BDC_OKCODE'

'/00'.

PERFORM bdc_field USING 'BDC_CURSOR'

'MAKT-MAKTX'.

• Purchasing View

PERFORM bdc_dynpro USING 'SAPLMGMM' '4000'.

PERFORM bdc_field USING 'BDC_OKCODE'

'=BU'.

PERFORM bdc_field USING 'MARC-EKGRP'

i_mat-ekgrp.

• Call The Transaction

PERFORM bdc_transaction USING 'MM01'.

ENDLOOP.

• Close the BDC Session

PERFORM close_group.

kindly reward if helpful.

cheers,

Hema.

[Former Member]

Give me your Mail ID. I will send you the step by step document for creation of idoc.

Reward points if it helps.

[Former Member]

yusuftunay@gmail.com Thanks

[Former Member]

Hi,

The material master maintenance is used here as an example to explain how master data is distributed. All the scenarios for master data distribution are constructed in a similar way to the material master data distribution.

The material master maintenance and material master maintenance (copy) function types are located in distributed systems.

If maintenance is central, copy management is performed directly in the decentralized systems. If there are several maintenance systems (for example, one for each view of the material), copy management is handled in the reference system. The reference system then distributes the master data changes to all the other decentralized systems.

Messages can be sent in one two ways:

· If PUSH type distribution is used, data is exchanged using the MATMAS message type. (This message contains the material master data to be distributed).

· If PULL type distribution is used, the MATFET message type is sent from the material master copy management to the material master maintenance original. (This message is a request to the original to send material master data.)

The following filters control the distribution:

· Classes (for example, distributing classified material numbers to specific systems).

· Filter objects: organizational units (sales organization, plant).

As part of the ALE Customizing process the customer specifies in the distribution model which fields in which application table are relevant to the distribution for each message type

regards,

vasavi.

reward if helpful.

[Former Member]

Hi ,

here is MM Process flow:

The typical procurement cycle for a service or material consists of the following phases:

1. Determination of Requirements

Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.

2. Source Determination

The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.

3. Vendor Selection and Comparison of Quotations

The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.

4. Purchase Order Processing

The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.

5. Purchase Order Follow-Up

The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.

6. Goods Receiving and Inventory Management (GR)

Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.

7. Invoice Verification (IV)

The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.

regrds,vasavi.

reward if helpful.