Master data for "Purchasing Document category" 0DOC_CAT

Hello All,
I have a requirement to display the purchasing document category "0DOC_CAT" and its description in a report. The problem I am facing right now is:
How to get the Description or TEXT of the Purchasing document category ?
Is there any standard text master data datasource available ?
Is there any ECC tables which has this information ( both key and text).... as I searched through number of tables like T161T etc... but it only has the Key information (BSTYP)
Please let me know your ideas ....... Really appreciate your time........

Hi Ram,
In the source system, this feild is used along with document type and hence into BI we can use the table mentioned by you, that T161T only can be used to load text of document type along with document categ as compunded object.
For your info....you may be able to see some text for document categ (BSTYP) in ECC, thats because in the definition of this feild, the text is hard coded. If you would like then the same can be done in BI as well, by manually maintaining the text in the info object, in stead of loading.
In ECC the hard coded values are stored in Data dictionary tables, in this case in DD07D table, but this cant be used for data source.
Naveen.A

Similar Messages

  • Custom master data for Sales Document Number

    Is it possible to create master data for "sales document number" as a custom field and/or table in R/3?  We have a need to record the "end user" customer of an order but this data may be updated a long time after the order and sale is complete.  IT seems that loading to BW/BI may be simpler if this is treated as document attributes rather than transactional data since no delta will be trigger by changes to this field.  Does anyone have experience with this approach?

    Hi,
    it is possible to create attributes for this InfoObject. Add the Attributes you need in BW. You can use the attributes even if the sales doc is line item dimension of your cube.
    On Sourcesystem side you have to create a generic extractor in SBIW. I think a table view on VBAK or VBAP may fullfill your needs. Of course the tables are not the smallest ones but maybe u can use the timestamp to implement a generic delta. Check whether the timestamp is set when the 'end user' is set. Not every change in the sales document leads to an entry in the delta queue of logistic, but the timestamp should be set.
    After that replicate the datasource to BI and connect it to the attributes of 0SALES_DOC
    I had a similar enhancement at one customer reading the actual transport routes to the sales documents and it worked fine.
    Hope that helps
    Christoph Vortkamp

  • Error "Account assignment 00 for  purchase document does not exist " when u

    Hai,
    I am encountering the following problem when posting a PO based Invoice using BAPI_INCOMINGINVOICE_CREATE.
    The error says " account assignment 00 for purchasing document does not exist".
    The scenario is very simple.  I need to raise an Invoice against a PO. the PO has a single line item of quantity 10 net price 10.  Tax code is U2 ( 7% tax).
    I am passing the following at header level.
    Invoice_indicator ( as 'X'),company code,doc date , posting date, gross amount (107, currency USD, calc tax indicator as 'X'.
    At line item i am passing Invoice document item 000001, po number , po item number, tax code(U2) item amount (100),
    Does this error has got any thing to relate configuration matters?
    Regards,
    Upender

    Hi Upender,
    In some cases, depending on the type of PO / Posting,
    you might have to populate the accounting data itab and pass in the BAPI parameter.
    you can select the accounting data from EKKN for the PO.
    Again it depends on the PO category, wether you need to populate Qty & Unit in accounting data.
    Further, the accounting data should be exactly the same as there in EKKN ( all the fields except Qty & Unit ).
    Thanks,
    Ram

  • What are the T-codes that contain the master data for material and vendor?

    what are the T-codes that contain the master data for material and vendor?

    hi ,
    - Display Material  tcodes...
    MM01 - Create Material
    MM02 - Change Material
    MM03 - Display Material
    MM50 - List Extendable Materials
    MMBE - Stock Overview
    MMI1 - Create Operating Supplies
    MMN1 - Create Non-Stock Material
    MMS1 - Create Service
    MMU1 - Create Non-Valuated Material
    ME51N - Create Purchase Requisition
    ME52N - Change Purchase Requisition
    ME53N - Display Purchase Requisition
    ME5A - Purchase Requisitions: List Display
    ME5J - Purchase Requisitions for Project
    ME5K - Requisitions by Account Assignment
    MELB - Purch. Transactions by Tracking No.
    ME56 - Assign Source to Purch. Requisition
    ME57 - Assign and Process Requisitions
    ME58 - Ordering: Assigned Requisitions
    ME59 - Automatic Generation of POs
    ME54 - Release Purchase Requisition
    ME55 - Collective Release of Purchase Reqs.
    ME5F - Release Reminder: Purch. Requisition
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MBRL - Return Delivery per Mat. Document
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB1B - Transfer Posting
    MIBC - ABC Analysis for Cycle Counting
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI21 - Print physical inventory document
    MI04 - Enter Inventory Count with Document
    MI05 - Change Inventory Count
    MI06 - Display Inventory Count
    MI09 - Enter Inventory Count w/o Document
    MI34 - Batch Input: Enter Count
    MI35 - Batch Input: Post Zero Stock Balance
    MI38 - Batch Input: Count and Differences
    MI39 - Batch Input: Document and Count
    MI40 - Batch Input: Doc., Count and Diff.
    MI08 - Create List of Differences with Doc.
    MI10 - Create List of Differences w/o Doc.
    MI20 - Print List of Differences
    MI11 - Physical Inventory Document Recount
    MI07 - Process List of Differences
    MI37 - Batch Input: Post Differences
    for vendor..
    XKN1  Display Number Ranges (Vendor)
    XK01  Create vendor (centrally)
    XK02  Change vendor (centrally)
    XK03  Display vendor (centrally)
    XK04  Vendor Changes (Centrally)
    XK05  Block Vendor (Centrally)
    XK06 Mark vendor for deletion (centrally
    XK07  Change vendor account group
    XK11  Create Condition
    XK12  Change Condition
    XK13  Display Condition
    XK14  Create with cond. ref. (cond. list)
    XK15  Create Conditions (background job)
    reward points if useful,
    venkat.

  • Due List for Purchasing Documents

    Dear Experts,
    I'm implementing SMI scenario with SAP SNC 5.1. I was traying to create an ASN, for a Replenishment Order already created, using "Due List for Purchasing Documents" screen, but when I insert the data to filter the list the following error will appear me:
    ODM error while loading releases
    What it means? How can I solve it?
    Thank you in advance.
    Edited by: PTP Team Consultants on Dec 5, 2011 5:24 PM

    Hi Vinod,
    thanks for the answer but I already implemented that note.
    Any other solutions?
    Thank you

  • Search by partner function for purchasing documents?

    Hello,
    Please could someone advise the steps required to allow me to search via partner function for purchasing documents? The functionality is present in IH08 for PM.

    Hi dear,
    During defining the partner Schema, please follow the process:
    a.Create partner Schema
    b.After creation of partner Schema, select your partner Schema and click u201Cpartner roles in schemau201D and you will have next screen
    Now for Partner function like VN,OA,PI and GS as you required and select the check box of mandatory
    and save.
    Now try creating Vendor and you will have Partner function like VN,OA,PI and GS in vendor master.
    Note: The following configuration steps for Vendor master are:
    1. Create Vendor Account Group.OBD3
    2. Maintain Number Ranges from Vendor account Group:XKN1,
    3.Assignment of Number ranges to Account Group,OBAS
    4.Partner Function: SPRO->MM->Purcahsing->Partner Determination-> partner roles->Permissible partner role sper account group
    5.Partner Schema:
    SPRO->MM->Purcahsing->Partner Determination->Partner setting in Vendor master record-> Define partner Schema
    6.Assgin partner schema to accont Group
    SPRO->MM->Purcahsing->Partner Determination->Partner setting in Vendor master record-> Assgin partner schema to account Group.

  • Master data for warehouse management

    Hi experts what are the master data for the warehouse
    management module.............

    Hi
    Sending you all the table for the warehouse mangement.
    Inventory document
    IKPF Header: Physical Inventory Document
    ISEG Physical Inventory Document Items
    LINK Inventory document header in WM
    LINP Inventory document item in WM
    LINV Inventory data per quant
    Storage locations and stocks
    LAGP Storage bins
    LEIN Storage unit header records
    LQUA Quants
    LQUAB Total quant counts for certain strategies
    MEIK Make-to-Order Stock for Customer Order
    MSCA Sales Orders on Hand with Vendor
    MSKA Sales Order Stock
    MBPR Stock at Production Storage Bin
    MLGN Material Data per Warehouse Number
    MLGT Material Data per Storage Type
    Rewards if useful.
    with regards
    Nikunj Shah

  • Credit master data for Customer

    Hi,
    I need solution for the below problem.
    Credit master data for Customer "X" is not maintained.
    Is there any possibility to get the information /Error message during sales order creation/Save for Customer "X" as Credit master data is not maintain.
    Information/Error message shouldd be:No credit master data maintain for Customer "X"
    Thanks for your help.
    Regards,
    Balaji.

    Hi
    You can use the followig user exit which will perform a check while saving the order.
    Take the help of your abaper to write a code to check if the credit master has been maintained for the customer before saving the order.
    Program,: MV45AFZZ
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    Regards
    Madhu

  • Set Length in Inches in item master data in purchasing tab

    Dear Experts,
    I want to set the length,width and height in Inches in the item master data of purchasing data tab. By default it is coming in meter. Please help me
    Regards,
    Ravindra

    Hi Ravindra......
    Go to Administration --> System Initialization --> General Settings --> Display Tab --> Default Length UoM --> set in Inch.
    Hope this will solve your problem.......
    Regards,
    Rahul

  • Payment terms in Vendor Master data and purchasing info record

    Hi, all, I met one trouble. While I create Purchase Order. In the header item, payment terms is automatically pop up from the data maintaining the vendor master data or purchasing info record if there is difference payment terms between in vendor master data and in purchasing info record. What happend?
    Sometimes, When you create purchase order, payment terms is not automatically pop up even you maintained in the vendor master data or purchasing info record. Why? Is it meaning that I can manually to input payment terms while create each purchase order which can be difference data with vendor master data or purchase info record?
    Thank you very much in advance,

    Hi,
    The payment terms is usually defaulted from either vendor master or purchasing master data record such as contract/outline agreement.  Unless it is set through configuration that the payment terms be set as mandatory, any failure to maintain payment terms won't stop you from posting your PO as this information will only be useful during invoice receipt maintenance.  Having said that if you are setting up your system with discount condition type as part of your PO pricing schema then it is necessary that the payment terms shall be maintained during PO creation.
    Cheers,
    HT

  • Need BAPI to update posting date for parked documents in transaction FBV2?

    Hi All,
    I am retrieving records from table VBKPF and I have to update the posting date for parked documents in transaction FBV2.
    I am doing it with BDC , working fine in foreground, but it is not workung fine in back ground.I want to do this with bapi.
    Can any one suggest me corrct BAPI?
    TYPES : BEGIN OF It_vbkpf,
             bukrs LIKE vbkpf-bukrs,            "Company Code
             belnr LIKE vbkpf-belnr,            "document number
             gjahr LIKE vbkpf-gjahr ,           "Fiscal year
             budat LIKE vbkpf-budat,            "Posting date
             bldat LIKE vbkpf-bldat,            "Document date
             blart LIKE vbkpf-blart,            "Document type
             xblnr LIKE vbkpf-xblnr,            "Reference
             tcode LIKE vbkpf-tcode,            "Transaction Code
             bktxt LIKE vbkpf-bktxt,            "Document header text
             usnam LIKE vbkpf-usnam,            "User Name
             xwffr LIKE vbkpf-xwffr,            "Release necessary
             xprfg LIKE vbkpf-xprfg,            "Document complete
             xfrge LIKE vbkpf-xfrge,            "Release takes place
            END  OF it_vbkpf.
    Thanks,
    Suresh.

    Hi ,
    Thanks for your response.
    PRELIMINARY_POSTING_UPDATE seems working good,But my requirement here , to update the posting date with last working day . how can i do this?
    thanks,
    Suresh.

  • Report for Purchasing Documents with Over Delivery or Under Delivery Tolera

    Dear All !
    please suggest me a report for Purchasing Documents with Over Delivery or Under Delivery Tolerance limit.
    thanks n regards
    Naagsekhar

    hi,
    Go to ME2N --> Use dynamic selection, choose for hte Puchase doc item --> here select for the over and under delivery and then execute the report..
    Hope it helps..
    Regards
    Priyanka.P

  • Add additional field in Vendor master data for VAT Reg. No.?

    Add additional field in Vendor master data for VAT Reg. No.?
    Hi I need to add one additional field for other VAT Reg. number in vendor master data FK01, We currently have two field
    Current Settings:
    Country : LFAS-LAND1
    VAT registration no.: LFAS-STCEG
    I need to add one additional field for text information. Is this possible?
    Thanks you very much
    Luis G.

    If you want to add new fields that are not possible from config (check with your consultant) you need to implement BADIs
    In SPRO, go to:
    >Logistics-General
    ->Business Partner
    -->Vendors
    --->Control
    >Adoption of Cusomter's Own Master Data Fields
    and read the documentation provided there.
    You will need to implement following BAPIs
    Processing Master Data Enhancements: VENDOR_ADD_DATA
    Customer Subscreens: VENDOR_ADD_DATA_CS
    I am not aware of any other way to add new fields to Vendor master (however, check with your consultant for config related screen modifications)
    Should you need any further info to implement it, post back (read it thoroughly first, it's quite self-explanatory).
    regards,
    Aabhas

  • Updating Scheduling data for Purchase Order

    Hi,
    I need a function module which can update the scheduling data for purchase order in EKET table. Normally we create Purchase Order as a reference from purchase requisition through BAPI_PO_CREATE1. That time it takes care of all the scenarios. But as per the requirement I want to create a PO which is created from more than one Purchase Requistions so I can't use the said BAPI. But still I am using this BAPI and after creation is completed I am updating the Requistions. The same scenario is taken care in ME59N, but I can't copy that code because of some requirements. So could any one please give me the idea to replicate the same functionality with any function module or other ways.
    Thanks
    Somnath paul

    try to pass all u sheduling related fields to POSCHEDULE and make sure u have enabled POSCHEDULEX along with sheduling related fields .....also (if no changes  are there  leave it with space )...
    this will definetly update not only eket table ....it will update every table regarding to purchase order,ekpo,ekko,eket ...etc
    Example of population of BAPI interface in the Function
    Parameter: POHEADER
    COMP_CODE            =                    1000
    DOC_TYPE             =                    NB
    ITEM_INTVL           =                    00001
    VENDOR               =                    0000001000
    PMNTTRMS             =                     0001
    PURCH_ORG            =                     1000
    PUR_GROUP            =                     001
    CURRENCY             =                     EUR
    Parameter: POHEADERX
    COMP_CODE            =                     X
    DOC_TYPE             =                     X
    ITEM_INTVL           =                     X
    VENDOR               =                     X
    PMNTTRMS             =                     X
    PURCH_ORG            =                     X
    PUR_GROUP            =                     X
    Parameter: POITEM
    PO_ITEM              =                     00001
    MATERIAL             =                    100-100
    PLANT                =                    1000
    STGE_LOC             =                    0001
    QUANTITY             =                    15.000
    TAX_CODE             =                    V0
    ITEM_CAT             =                     0
    ACCTASSCAT           =                    K
      Parameter: POITEMX
      PO_ITEM              =                    00001
      MATERIAL             =                    X
      PLANT                =                    X
      STGE_LOC             =                    X
      QUANTITY             =                    X
      TAX_CODE             =                    X
      ITEM_CAT             =                    X
      ACCTASSCAT           =                    X
      Parameter: POSCHEDULE
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0001
      DELIVERY_DATE        =                    02.12.2002
      QUANTITY             =                    6.000
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0002
      DELIVERY_DATE        =                    03.12.2002
      QUANTITY             =                    5.000
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0003
      DELIVERY_DATE        =                    04.12.2002
      QUANTITY             =                    4.000
      Parameter: POSCHEDULEX
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0001
      PO_ITEMX             =                    X
      SCHED_LINEX          =                    X
      DELIVERY_DATE        =                    X
      QUANTITY             =                    X
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0002
    Parameter: POACCOUNT
    PO_ITEM              =                    00001
    SERIAL_NO            =                    01
    QUANTITY             =                    15.000
    GL_ACCOUNT           =                    0000400000
    COSTCENTER           =                    0000001000
    CO_AREA              =                    1000
    Parameter: POACCOUNTX
    PO_ITEM              =                    00001
    SERIAL_NO            =                    01
    QUANTITY             =                    X
    GL_ACCOUNT           =                    X
    COSTCENTER           =                    X
    CO_AREA              =                    X
    Parameter: POCOND
    ITM_NUMBER           =                    000001
    COND_ST_NO           =                    001
    COND_TYPE            =                    PB00
    COND_VALUE           =                    79.900000000
    CURRENCY             =                    EUR
    CURRENCY_ISO         =                    EUR
    COND_UNIT            =                    KG
    COND_P_UNT           =                    1
    CHANGE_ID            =                    U
    Parameter: POCONDX
    ITM_NUMBER           =                    000001
    COND_ST_NO           =                    000
    ITM_NUMBERX          =                    X
    COND_TYPE            =                    X
    COND_VALUE           =                    X
    CURRENCY             =                    X
    CHANGE_ID            =                    X
    Parameter: POPARTNER
    PARTNERDESC          =                    OA
    LANGU                =                    EN
    BUSPARTNO            =                    0000001100
    PARTNERDESC          =                    GS
    LANGU                =                    EN
    BUSPARTNO            =                    0000001200
    PARTNERDESC          =                    PI
    LANGU                =                    EN
    BUSPARTNO            =                    0000001000
    reward points if helpful....

  • MRRL- Item 00002 for purchasing document not selectable

    I have a PO which was created with ERS flag on, when we did GR we realized this should not be ERS activated PO. So we reverse the GR  and unchecked the Inv. receiptm GR based IV and ERS flag on the PO but now this PO is keep showing up in MRRL with a message "Item 00002 for purchasing document not selectable". How do i get rid off this PO from MRRL report.
    Please help!

    When an item is marked as ERS and a GR is done an entry is put in the EKRS table.   My guess is that you did not do a settlement after you did the reversal so the EKRS table still has the original GR and the reversal which is why it is showing up when you execute MRRL.    If you don't want that showing up when you execute MRRL I would add the ERS flag back long enough to do a settlement.   The settlement will create a zero value MM invoice and clear out those two entries in the EKRS table.   
    Regards,
    Sandra

Maybe you are looking for