Importing Material data

Hi,
We have decided to import all the master data elements using the enterprise and Sourcing WB for CLM implementation.
For material import, if a material exists for multiple plants which is a required field, is it reqd to create multiple entries with plant codes or else can we have the material with one plant code and then later during contract creation, can the plant detail be changed?
request your pointers.
Rgds,
Madhan

Hi Madhan
A suggested by Vikram you need to maintain three material records. however for user convenience you can give the same DISPLAY_NAME to all the materials maintaining EXTERNAL_ID as Plant Name_Material Name, since external ID is used as the unique identifier.
This way when users would have to choose the materials in Rfx, Auction or MA, they would see the same material name distinguished by Plant name which would be easier for them to comprehend.
Regards
Mudit Saini

Similar Messages

Importing Material Data step-by-step instructions

Hi,
I am using SAP MDM 5.5.24.06 and trying to import Material data (XML / Idoc format) that was extracted from R/3 using Transaction MDM_CLNT_EXTR.
I used MATMAS.MATMAS04.xsd schema and selected MATMAS04_R3 mapping but MDM IM returned errors for bunch fields and not able to import data.
Has anybody been successful in importing R/3 data into MDM?
Would you please share the deail steps that (with configuration values entered/selected, field/data mappings ) need to be follow in Import Manager or in MDM Console component?
Thanks,
Abhay

Abhay,
I started doing it, however due to Tech Ed Vienna, I have not completed the same.
However, if you are using the transaction MDM_CLNT_EXTR I remember it will throw out an IDOC type of MDM_RECEIPT (not sure of the spelling).
So, your MATMAST04 XSD , I don'think it will work. However I am not sure, You will have to check it out.
Regards,
Ravi

Export and Import Material data (MM01)

Hi,
I would like to know if it's possible to export all the data of the material master data from one system to import in another one ?
I thought about a program that create data like the LSMW standard program. But I didn't find the oposite of the RMDATIND.
I thought about IDoc, but I'm not sure it's possible.
Please don't speak about SE16
Thanks
Fred

1. Yes, we used external "number" range for the material number.
2. Yes, we have extend, but it's not important for me.
My big question is :
- What message type I have to use ?
- Do I have to create RFC connexion or could I just copy the file ?
It's 2 SAP System, and it's not the same system. (Developpment -> Quality).
Message was edited by: Frédéric Girod

Automatic import of material data (csv file) from FTP directory

Hello Experts,
We created a Scheduled Task -> Data Import Monitor -> from a FTP directory.
We loaded the .csv file with material data in the FTP folder but it is not getting imported.We have created the .csv file with the format of fields defined in Company quick start Work book -> Material tab. We also tried with a .csv file having first Field as CLASS_NAME with a value of masterdata.Material and rest of the fields same as defined in the Company quick start-Materials Tab still it did not work.
When we load the .xls work book in FTP directory (xl having the Configuration tab and Material tab) the data import is working fine and the data is getting loaded automatically from the data import monitor job.
Is there any specific format of .csv file in which the material data needs to be loaded to the FTP server for automatic import of data using Scheduled task?
Regards
Aditya

Are there any errors appearing in the FPA logs?
Have you checked the permissions on the folder/file that you are uploading from?
What type of scheduled task have you created?

Error during BAPI while uploading Material data through MM01

Hi all,
i am facing one problem when uploading Material data thorough BAPI in MM01.i am attaching the code below and the error given.
but in the debugger all the value is being stored.
REPORT ZFINISHED_MAT.
Data: Begin of legacy_data occurs 0,
     MATNR LIKE MARA-MATNR,
     MBRSH LIKE MARA-MBRSH,            "Industry Sector
     MTART LIKE MARA-MTART,            "Matl Type
     WERKS LIKE MARD-WERKS,            "Plant
     LGORT LIKE MARD-LGORT,            "Storage location
     VKORG LIKE MVKE-VKORG,
     VTWEG LIKE MVKE-VTWEG,
     MAKTX LIKE MAKT-MAKTX,             "Matl Desc.
     MEINS LIKE MARA-MEINS,             "Base UOM
     MATKL LIKE MARA-MATKL,             "Matl.Grp
*     BISMT LIKE MARA-BISMT,
     SPART LIKE MARA-SPART,             "Division
*     BRGEW LIKE MARA-BRGEW,             "Gross weight
     GROES LIKE MARA-GROES,
     FERTH LIKE MARA-FERTH,
     ZEINR LIKE MARA-ZEINR,
     TAXKM1 LIKE MLAN-TAXM1,
     TAXKM2 LIKE MLAN-TAXM2,
     TAXKM3 LIKE MLAN-TAXM3,
     TAXKM4 LIKE MLAN-TAXM4,
     KTGRM LIKE MVKE-KTGRM,
*     GEWEI LIKE MARA-GEWEI,             "Weight unit
*     NTGEW LIKE MARA-NTGEW,             "Net weight
*     KLART LIKE RMCLF-KLART,
     MTVFP LIKE MARC-MTVFP,             "Availibility Check
*     XGCHP LIKE MARA-XGCHP,
     XCHPF LIKE MARA-XCHPF,             "Batch Management
     TRAGR LIKE MARA-TRAGR,
     LADGR TYPE MARC-LADGR,
     VPRSV LIKE MBEW-VPRSV,            "Price Control
     VERPR LIKE MBEW-VERPR,
*     SPRAS LIKE MAKT-SPRAS,
END OF LEGACY_DATA.
DATA: BEGIN OF IT_MAKT OCCURS 0.
INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF IT_MAKT.
*--- BAPI structures
DATA: BAPI_HEAD LIKE BAPIMATHEAD, " Header Segment with Control Information
BAPI_MAKT LIKE BAPI_MAKT, " Material Description
BAPI_MARA1 LIKE BAPI_MARA, " Client Data
BAPI_MARAX LIKE BAPI_MARAX, " Checkbox Structure for BAPI_MARA
BAPI_MARD1 LIKE BAPI_MARD,
BAPI_MARDX1 LIKE BAPI_MARDX, " Checkbox Structure for BAPI_MARD
BAPI_MARC1 LIKE BAPI_MARC, " Plant View
BAPI_MARCX LIKE BAPI_MARCX, " Checkbox Structure for BAPI_MARC
BAPI_MVKE1 LIKE BAPI_MVKE,
BAPI_MVKEX1 LIKE BAPI_MVKEX, " Checkbox Structure for BAPI_MVKE
BAPI_MLAN1 LIKE BAPI_MLAN,
BAPI_MLANX1 LIKE bapi_mlan1, " Checkbox Structure for BAPI_MLAN
BAPI_MBEW1 LIKE BAPI_MBEW, " Accounting View
BAPI_MBEWX LIKE BAPI_MBEWX, " Checkbox Structure for BAPI_MBEW
BAPI_RETURN LIKE BAPIRET2. " Return Parameter
*              $PARAMETERS DECLARATION$
SELECTION-SCREEN BEGIN OF BLOCK B11
                          WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME. " DEFAULT 'C:\TEST1.XLS'.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN ULINE.
SELECTION-SCREEN END OF BLOCK B11 .
*              $DATA DECLARATION$
*DATA : BDC_DATA LIKE STANDARD TABLE OF BDCDATA WITH HEADER LINE.
DATA : IT_EXCEL TYPE STANDARD TABLE OF ALSMEX_TABLINE INITIAL SIZE 0 WITH HEADER LINE,
        IT_EXCEL_DUMMY TYPE ALSMEX_TABLINE.
DATA : MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : L_MSTRING(480).
DATA :L_SUBRC LIKE SY-SUBRC.
DATA: V_FILE TYPE STRING.
*              $AT-SELECTON SCREEN DECLARATION$
AT SELECTION-SCREEN ON P_FILE.
IF P_FILE IS INITIAL.
    MESSAGE E398(00) WITH 'FILE NAME NEEDS TO BE SPECIFIED'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
CALL FUNCTION 'F4_FILENAME'
   EXPORTING
     PROGRAM_NAME        = SYST-CPROG
*   DYNPRO_NUMBER       = SYST-DYNNR
     FIELD_NAME          = 'P_FILE'
   IMPORTING
     FILE_NAME           = P_FILE
start-of-selection.
perform data_fetch_to_xls.
perform insertion.
*&      Form data_fetch_to_xls
*       text
* --> p1        text
* <-- p2        text
FORM data_fetch_to_xls .
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      FILENAME                = P_FILE
      I_BEGIN_COL             = 1
      I_BEGIN_ROW             = 2
      I_END_COL               = 25
      I_END_ROW               = 2
    TABLES
      INTERN                  = IT_EXCEL
    EXCEPTIONS
      INCONSISTENT_PARAMETERS = 1
      UPLOAD_OLE              = 2
      OTHERS                  = 3.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    WRITE: /'ERROR UPLOADING XLS FILE FROM PRESENTATION SERVER !' ,
           /'RETURN CODE : ', SY-SUBRC.
ELSE.
*************NOW FILL DATA FROM EXCEL INTO FINAL LEGACY DATA ITAB----LEGACY_DATA***************
    IF NOT IT_EXCEL[] IS INITIAL.
      CLEAR LEGACY_DATA.
      REFRESH LEGACY_DATA[].
      LOOP AT IT_EXCEL.
        IT_EXCEL_DUMMY = IT_EXCEL.
        AT NEW COL.
          CASE IT_EXCEL_DUMMY-COL.
            WHEN 1.
              LEGACY_DATA-MATNR = IT_EXCEL_DUMMY-VALUE(18).
            WHEN 2.
              LEGACY_DATA-MBRSH = IT_EXCEL_DUMMY-VALUE(1).
            WHEN 3.
              LEGACY_DATA-MTART = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 4.
              LEGACY_DATA-WERKS = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 5.
              LEGACY_DATA-LGORT = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 6.
              LEGACY_DATA-VKORG = IT_EXCEL_DUMMY-VALUE(4).
             WHEN 7.
              LEGACY_DATA-VTWEG = IT_EXCEL_DUMMY-VALUE(2).
            WHEN 8.
              LEGACY_DATA-MAKTX = IT_EXCEL_DUMMY-VALUE(40).
            WHEN 9.
              LEGACY_DATA-MEINS = IT_EXCEL_DUMMY-VALUE(3).
            WHEN 10.
              LEGACY_DATA-MATKL = IT_EXCEL_DUMMY-VALUE(9).
            WHEN 11.
              LEGACY_DATA-SPART = IT_EXCEL_DUMMY-VALUE(2).
            WHEN 12.
              LEGACY_DATA-GROES = IT_EXCEL_DUMMY-VALUE(32).
            WHEN 13.
              LEGACY_DATA-FERTH = IT_EXCEL_DUMMY-VALUE(18).
            WHEN 14.
              LEGACY_DATA-ZEINR = IT_EXCEL_DUMMY-VALUE(22).
             WHEN 15.
              LEGACY_DATA-TAXKM1 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 16.
              LEGACY_DATA-TAXKM2 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 17.
              LEGACY_DATA-TAXKM3 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 18.
              LEGACY_DATA-TAXKM4 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 19.
              LEGACY_DATA-KTGRM = IT_EXCEL_DUMMY-VALUE(2).
            WHEN 20.
              LEGACY_DATA-MTVFP = IT_EXCEL_DUMMY-VALUE(2).
             WHEN 21.
              LEGACY_DATA-XCHPF = IT_EXCEL_DUMMY-VALUE(1).
            WHEN 22.
              LEGACY_DATA-TRAGR = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 23.
              LEGACY_DATA-LADGR = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 24.
              LEGACY_DATA-VPRSV = IT_EXCEL_DUMMY-VALUE(1).
            WHEN 25.
              LEGACY_DATA-VERPR = IT_EXCEL_DUMMY-VALUE(14).
              APPEND LEGACY_DATA.
              CLEAR LEGACY_DATA.
          ENDCASE.
        ENDAT.
        AT END OF ROW.
        ENDAT.
      ENDLOOP.
    ENDIF.
ENDIF.
ENDFORM.                    " data_fetch_to_xls
*&      Form insertion
*       text
* --> p1        text
* <-- p2        text
FORM insertion .
LOOP AT legacy_data.
* Header
BAPI_HEAD-MATERIAL = legacy_data-MATNR.
BAPI_HEAD-IND_SECTOR = legacy_data-MBRSH.
BAPI_HEAD-MATL_TYPE = legacy_data-MTART.
BAPI_HEAD-BASIC_VIEW = 'X'.
BAPI_HEAD-SALES_VIEW = 'X'.
BAPI_HEAD-STORAGE_VIEW = 'X'.
*BAPI_HEAD-PURCHASE_VIEW = 'X'.
BAPI_HEAD-ACCOUNT_VIEW = 'X'.
* Material Description
REFRESH IT_MAKT.
*IT_MAKT-LANGU = legacy_data-SPRAS.
IT_MAKT-MATL_DESC = legacy_data-MAKTX.
APPEND IT_MAKT.
BAPI_MARD1-PLANT = legacy_data-WERKS.
BAPI_MARD1-STGE_LOC = legacy_data-LGORT.
BAPI_MARDX1-PLANT = legacy_data-WERKS.
BAPI_MARDX1-STGE_LOC = legacy_data-LGORT.
** Client Data - Basic
BAPI_MARA1-MATL_GROUP = legacy_data-MATKL.
*bapi_mara1-OLD_MAT_NO = legacy_data-bismt.
BAPI_MARA1-BASE_UOM = legacy_data-MEINS.
BAPI_MARA1-PROD_MEMO = LEGACY_DATA-FERTH.
BAPI_MARA1-SIZE_DIM = LEGACY_DATA-GROES.
BAPI_MARA1-DOCUMENT = LEGACY_DATA-ZEINR.
BAPI_MARA1-BATCH_MGMT = LEGACY_DATA-XCHPF.
*BAPI_MARA1-UNIT_OF_WT = legacy_data-GEWEI.
BAPI_MARA1-TRANS_GRP = legacy_data-TRAGR.
BAPI_MARA1-DIVISION = legacy_data-SPART.
BAPI_MARAX-MATL_GROUP = 'X'.
*BAPI_MARAX-OLD_MAT_NO = 'X'.
BAPI_MARAX-BASE_UOM = 'X'.
BAPI_MARAX-PROD_MEMO = 'X'.
BAPI_MARAX-SIZE_DIM = 'X'.
BAPI_MARAX-DOCUMENT = 'X'.
BAPI_MARAX-BATCH_MGMT = 'X'.
*BAPI_MARAX-UNIT_OF_WT = 'X'.
BAPI_MARAX-TRANS_GRP = 'X'.
BAPI_MARAX-DIVISION = 'X'.
*SALES
BAPI_MVKE1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKE1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKE1-DELYG_PLNT = legacy_data-DWERK.
BAPI_MVKE1-ACCT_ASSGT = legacy_data-KTGRM.
BAPI_MVKEX1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKEX1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKEX1-DELYG_PLNT = 'X'.
BAPI_MVKEX1-ACCT_ASSGT = 'X'.
** Plant - Purchasing
BAPI_MARC1-PLANT = legacy_data-WERKS.
BAPI_MARC1-LOADINGGRP = legacy_data-LADGR.
BAPI_MARC1-AVAILCHECK = legacy_data-MTVFP.
*BAPI_MARC1-MRP_GROUP = legacy_data-disgr.
BAPI_MARCX-PLANT = legacy_data-WERKS.
BAPI_MARCX-LOADINGGRP = 'X'.
BAPI_MARCX-AVAILCHECK = 'X'.
*BAPI_MARCX-MRP_GROUP = 'X'.
* Accounting
BAPI_MBEW1-VAL_AREA = legacy_data-WERKS.
BAPI_MBEW1-PRICE_CTRL = legacy_data-VPRSV.
BAPI_MBEW1-STD_PRICE = legacy_data-VERPR.
*BAPI_MBEW1-VAL_CLASS = legacy_data-BKLAS.
*BAPI_MBEW1-STD_PRICE = legacy_data-STPRS.
*BAPI_MBEW1-PRICE_UNIT = legacy_data-PEINH.
BAPI_MBEWX-VAL_AREA = legacy_data-WERKS.
BAPI_MBEWX-PRICE_CTRL = 'X'.
BAPI_MBEWX-STD_PRICE = 'X'.
*BAPI_MBEWX-VAL_CLASS = 'X'.
* TAX JURISDICTION CODE
BAPI_MLAN1-TAXCLASS_1 = LEGACY_DATA-TAXKM1.
BAPI_MLAN1-TAXCLASS_2 = LEGACY_DATA-TAXKM2.
BAPI_MLAN1-TAXCLASS_3 = LEGACY_DATA-TAXKM3.
BAPI_MLAN1-TAXCLASS_4 = LEGACY_DATA-TAXKM4.
BAPI_MLAN1-TAXCLASS_1 = 'X'.
BAPI_MLAN1-TAXCLASS_2 = 'X'.
BAPI_MLAN1-TAXCLASS_3 = 'X'.
BAPI_MLAN1-TAXCLASS_4 = 'X'.
*--- BAPI to create material
call function 'BAPI_MATERIAL_SAVEDATA'
exporting
HEADDATA = BAPI_HEAD
CLIENTDATA = BAPI_MARA1
CLIENTDATAX = BAPI_MARAX
*PLANTDATA = BAPI_MARC1
*PLANTDATAX = BAPI_MARCX
* FORECASTPARAMETERS =
* FORECASTPARAMETERSX =
* PLANNINGDATA =
* PLANNINGDATAX =
* STORAGELOCATIONDATA =
* STORAGELOCATIONDATAX =
VALUATIONDATA = BAPI_MBEW1
VALUATIONDATAX = BAPI_MBEWX
* WAREHOUSENUMBERDATA =
* WAREHOUSENUMBERDATAX =
* SALESDATA = BAPI_MVKE1
* SALESDATAX = BAPI_MVKEX
* STORAGETYPEDATA =
* STORAGETYPEDATAX =
IMPORTING
RETURN = BAPI_RETURN
TABLES
MATERIALDESCRIPTION = IT_MAKT
* UNITSOFMEASURE =
* UNITSOFMEASUREX =
* INTERNATIONALARTNOS =
* MATERIALLONGTEXT =
* TAXCLASSIFICATIONS =
* RETURNMESSAGES =
* PRTDATA =
* PRTDATAX =
* EXTENSIONIN =
* EXTENSIONINX =
IF BAPI_RETURN-TYPE = 'E'.
WRITE:/ 'Error:' ,BAPI_RETURN-MESSAGE ,'for material:' ,legacy_data-maTNR.
ELSEIF BAPI_RETURN-TYPE = 'S'.
WRITE: 'Successfully created material' ,legacy_data-maTNR.
ENDIF.
ENDLOOP.
ENDFORM.                    " insertion
The error: The field MARC-MTVFP/BAPI_MARC-AVAILCHECK is defined as a required field; it does not contain an entr
suggestion will be vry helpful,
Kind Regards,
Edited by: Prasenjit Sengupta on Nov 16, 2009 9:11 AM

Hi Prasenjit,
Did you get any solution for this as I am getting same error from BAPI to update MRP controller in MARC table.
Regards,
Suruchi

Import material tracking

Hi All,
Following client requirement needed to be mapped,, For import material the invetroy tracking is needed in following places.
Stock of material before arrives the port in container yard (shipping lines), in our container yard and stock in our plant. As of now we do GRN in plant only.Soplease let me know how to track all these in inventroy with or without inbound delivery.
Suggetions hoghly appriciated.
RB

Dear,
Tracking Import.
First enter XK01 - Create Vendor, in purchasing view you can assign Confirmation Control Key - 0004 - Tracking import.
If vendor is already create, then enter XK02 - change vendor and maintain it in purchasing view.
So at the time of purchase order creation - ME21N system take by default tracking import in purchase order -> Conformation tab -> confirmation control -> Tracking Import.
You can maintain below mention status in Tracking Import,
Acknowledge by Vendor
Dispatched by Vendor
Arrived at Port
Clearance at Port
Stocked at Port
Dispatch. to Factory
After maintain this you can map all process of import purchase.
Exa: - If you purchase material from import market and you prepaid import purchase order - ME21N and maintain tracking import in purchase order.
Then maintain vendor acknowledge when vendor receive your purchase order.
You can maintain dispatch detail by vendor at the time of vendor dispatch etc.
Due to this you can find out actual status of import purchase.
If in your company tracking import is not activated.
So you can config it with below path.
SPRO - Materials Management - Purchasing - Purchase Order - Confirmations - Define External Confirmation Categories.
Here you can define status of tracking import like
Acknowledge by Vendor
Dispatched by Vendor
Arrived at Port
Clearance at Port
Stocked at Port
Dispatch. to Factory.
SPRO - Materials Management - Purchasing - Purchase Order - Confirmations - Define Internal Confirmation Categories.
Here active Order Acknowledgment - Z1 - Acknowledge by Vendor.
Then
SPRO - Materials Management - Purchasing - Purchase Order - Confirmations - Set Up Confirmation Control.
Create Tracking Import - 0004 and assign confirmation sequence.
Acknowledge by Vendor
Dispatched by Vendor
Arrived at Port
Clearance at Port
Stocked at Port
Dispatch. to Factory
At last record Dispatch to Factory, Here click on three indicators as per below mention detail,
Indicator for MRP - Relevant
Indicator for GR - Relevant
Indicator for GR - Assignment,
Also assign Reference date.
Then follow above mention process.
Regards,
Mahesh Wagh

Import material moving average price is showing negitive.

Dear GURUS
I have aproblem in Import material moving average price problem
My user put the amount 10000 EUROS instead of 10000 INR in P.O ,
I am getting the below mentioned error.
Moving average price for material is negative: 2428014263 1100 SPR_IMP
Message no. M8783
Diagnosis
     This item would create a stock value posting which would result in a
     negative moving average price for the material.
     Note:
     The category of this message can be changed in Customizing for Invoice
     Verification. This means that you can receive a message as an error
     message even though it is defined as a warning message in the standard
     system.
     The following documentation deals with the case applicable to the
     standard system only.
System Response
The system does not allow a negative moving average price.
cedure
Check your entry in the field "Amount" and correct it if necessary.
If your entry is correct, check the following for the material
o   the stock value
     (Environment -> Master data info -> Display material)
o   the posting history
     (Environment -> Line items -> For material).
It might be necessary to cancel past postings (for example, incorrectly
valuated goods receipts or incorrect price changes), before you can
carry out your posting.
If you wish to carry out a price change, the total stock of the material
may be negative. A price cannot be changed if the stock is negative.
Regards
srinivas

Dear,
Please refer the below SAP notes
SAP Note 356757-MR01, MR1M, MIRO: M8783 when posting invoices
SAP Note 753286 - Moving average price becomes very small
Regards,
Gopala.S

Foreign trade import/export data is getting copied when creating MMR

Hi,
When trying to create material master record with reference material ,the" Foreign trade import/export data " is not available in selection but the material is getting created with the "foreign data".
When to restrict so that the material master record gets created without "foreign trade data"
Thank you.

HI,
When u enter the new material,matl type & industry u enter the reference material and press enter then it shows the select views screen in this deselect the foreign trade tab and press enter then create material.The foreign data tab will not be copied in the new material.
murugan

Which R/3 function Module is used to extract material data?

Hi,
Does someone know which FM is used in R/3 to extract the material data when the replication object 'MATERIAL' is executed?
Thanks,
Jeroen

Hi,
You can write similar to the below.
CALL FUNCTION 'CRM_ORDER_READ'
<b>DESTINATION 'DERCLNT200'</b>
EXPORTING
it_header_guid = lt_header_guid
IMPORTING
et_orderadm_i = lt_orderadm_i_buffer
et_customer_i = lt_customer_i_buffer
CHANGING
cv_log_handle = lt_log_handle
EXCEPTIONS
document_not_found = 1
error_occurred = 2
document_locked = 3
no_change_authority = 4
no_display_authority = 5
no_change_allowed = 6
OTHERS = 7.
Thanks
Ramakrishna

BAPI to read material data

Hello,
I am looking for a function modul to read material data.
We want to export the data so we can import it into an WebShop Software.
We need material infos like text, price, sales text and so on.
Thanks
A. Dötsch

Hi A. Dötsch,
You can use BAPI_MATERIAL_GET_ALL
Regards,
ASA

Not enough space on my new SSD drive to import my data from time machine backup, how can I import my latest backup minus some big files?

I just got a new 256GB SSD drive for my mac, I want to import my data from time machine backup, but its larger than 256GB since it used to be on my old optical drive. How can I import my latest backup keeping out some big files on the external drive?

Hello Salemr,
When you restore from a Time Machine back up, you can tell it to not transfer folders like Desktop, Documents. Downloads, Movies, Music, Pictures and Public. Take a look at the article below for the steps to restore from your back up.
Move your data to a new Mac
http://support.apple.com/en-us/ht5872
Regards,
-Norm G.

Comments not imported from Data Dictionary of SQL Server. SDDM 3.3.0.747

Hi,
SDDM 3.3.0.747 32-bit on Windows 7 64-bit.
Comments are not imported from Data Dictionary of SQL Server 2008. Connection through Microsoft JDBC Driver 4.0 for SQL Server or jTDS 1.2.7
What I have tried? In SDDM DDL generation, Comments in DBRMS for SQL Server are generated with "EXEC sp_addextendedproperty 'MS_Description' , 'Test Comment' ..." so I added extended property named "MS_Description" into SQL Server database, both on table and column. None of them were imported from Data Dictionary into SSDM. I have tried both drivers stated above. Is it a bug or am I missing something?
I've found similar question thread Re: Data dictionary import doesn't import column comments for SDDM 3.0.0.665, so I guess it is a bug when importing with JDBC drivers.
MiGli
Edited by: MiGli_1006342 on May 25, 2013 8:32 AM
Edited by: MiGli_1006342 on May 25, 2013 9:02 AM

Extended properties were not imported correctly from SQLServer databases at DM 3.3.0.747.
Calls to sp_addextendedproperty and fn_listextendedproperty have been modified.
I don't think it is a problem with JDBC drivers.
A bug fix should be available in the next release of DM.

SQL modeler can not import from data dictionary

It was very frustruted to see that the SQL Modeler hang in import from data dictionary of a database as part of revise engineering. I have to question myself if sql modeler is a serious tool and should I give up.

I am not sure if Data Modeller is still in Beta./Production. First couple off initial versions of a new product are normally buggy.
Regards
Alternatively, If this product is still in Beta, then you can contact the development team or report the issue so that they can take care of this issue in next beta release.
Edited by: skvaish1 on Mar 30, 2010 3:18 PM
Edited by: skvaish1 on Mar 30, 2010 3:26 PM

Material field not getting displayed on Material Data tab in ME51n or ME21N

Material Field was missing in ME51n/ME21n.
I went into SPRO ->PReq-> Define Screen Layout at Document Level and checked Optional for Material field. Now it's showing up on the ITEM overview section of the Preq.
But its still missing on Material Data tab in ME51n or ME21N but I can see the Material field on the Item Overiew section of the Req/PO Screen.
Where exactly do I make the settings for the item level in SPRO?

We use the Enjoy screens and document types for ME51N/ME21N pretty much out of the box. We do not have the material master number on any of the detailed item tabs either. I do not think you can show it in the details unless you activate the customer specific fields tab.
Regards

How to get the salesprice and condition for a customer / material / date

Hi all,
how can I get the correct price and condition for a customer / material / date ?
I know this is possible using the BAPI_SALESORDER_SIMULATE, but this bapi is using to much ressources on the system.
I'm trying to get the correct price and condition WITHOUT using that BAPI.
Does anyone know how it is possible ? As said before : I have the customer, material and a date.
thanks in advance for your help

Hi
You need it because it's possible to have a complex pricing procedure, and you can't do it with a simple select on a table. Think that you can have pricing requirements, formulas (ie: VOFM) and so on in your pricing procedure (tcode V/08).
I hope this helps you
Regards
Eduardo

Importing Material data

Similar Messages

Maybe you are looking for