Accounts payable table relationship.

hi ,
         i want how the for bseg-belnr is related to material  no  matnr
please  if possible give me the details how fi and mm arerealted .

hi,
The FI - MM integration:
First you define the g/l master records.
1) Inventry raw material a/c
2) GR/IR clearing a/c
3) Raw material consumption a/c
Above like this you define all required g/l accounts
then you will go to T.CODE - OBYC 
Double click BSX (this is transaction key)
      "            GBB
      "            WRX
      "            PRD
These are transaction keys important.
Then you go to T CODE - OMSY (this is also important) then 
  Material creation T Code MM01 
  then 
1) Purchase order T.code  ME21N
2) Goods received     "       MIGO
3) Invoice verification  "      MIRO
given below r tables related to mm:
Common Tables used by SAP MM
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
SAP MM Tips by : Bahadur
Following are the list of Important MM tables. Please check if its useful.
Inventory Management:
Table
Description
Material
MSEG
Material document / transaction details
Document/Movements
MKPF
Material document header information
Material Stock Balances
MARD
Material stock
MBEW
Material stock with valuation
Sales Order Stock
MSKA
Stock balance with associated sales
order data
Stock Transport
EKUB
Index for Stock Transport Orders for
MDUB
Material
Reading View of Stock Transport Ord. for
Release Ord.
Special Stocks
MKOL
Consignment, material provided to
vendor, etc.
Material Master Data:
Table
Description
Materials
MARA
General Data, material type, group,
configurable & batch ind.
MAKT
Short Texts, descriptions
MARM
Conversion Factors
MVKE
Sales Org, distribution channel
MLAN
Sales data, tax indicator, tax
MARC
classification
MBEW
Plant Planning Data
MLGN
Valuation Data
MLGT
Warehouse Management Inventory Data
MVER
Warehouse Management Storage Type
MAPR
Data
MARD
Consumption Data
MCHA
Pointer for Forecast Data
MCHB
Storage location data with stock
balances
Batches
Batch Stocks
All The Tables In SAP MM Purchasing
Please find all tables in MM-PUR (Purchasing) :
EBAN  - Purchase Requisition 
EBKN  - Purchase Requisition Account Assignment 
EBUB   - Index for Stock Transport Requisitions for Materi
EINA    - Purchasing Info Record: General Data 
EINE     - Purchasing Info Record: Purchasing Organization D
EIPA     - Order Price History: Info Record 
EKAB   - Release Documentation 
EKAN   - Vendor Address: Purchasing Document 
EKBE    - History per Purchasing Document 
EKBEH - Removed PO History Records 
EKBZ    - History per Purchasing Document: Delivery Costs 
EKBZH  - History per Purchasing Document: Delivery Costs 
EKEH    - Scheduling Agreement Release Documentation 
EKEK    - Header Data for Scheduling Agreement Releases 
EKES     - Vendor Confirmations 
EKET     - Scheduling Agreement Schedule Lines 
EKETH   - Scheduling Agreement Schedules: History Tables 
EKKI      - Purchasing Condition Index 
EKKN    - Account Assignment in Purchasing Document 
EKKO    - Purchasing Document Header 
EKPA     - Partner Roles in Purchasing 
EKPB     - "Material Provided" Item in Purchasing Document 
EKPO    - Purchasing Document Item 
EKPV    - Shipping-Specific Data on Stock Tfr. for Purch. D 
EKRS    - ERS Procedure: Goods (Merchandise) Movements to b 
EKUB    - Index for Stock Transport Orders for Material 
EORD    - Purchasing Source List 
EQUK    - Quota File: Header 
EQUP     - Quota File: Item 
T024      - Purchasing Groups 
T024E    - Purchasing Organizations 
T024W   - Valid Purchasing Organizations for Plant 
T024Z    - Purchasing Organizations 
T027A    - Shipping Instructions, Purchasing 
T027B    - Texts: Shipping Instructions 
T027C    - Codes for Compliance with Shipping Instructions 
T027D    - Compliance with Shipping Instructions: Texts 
T069       - Certificate Categories 
T069Q    - Control Data for Source Determination and Checkin 
T069T     - Certificate Categories: Text Description 
T160       - SAP Transaction Control, Purchasing 
T160B     - SAP Transaction Control, List Displays, Purchasin 
T160C    -  SAP Transaction Control for List Displays in CALL 
T160D    - Function Authorizations: Purchase Order 
T160E     - Function Authorizations: Purchasing: Descriptions
T160I      - Control of Intrastat Reports 
T160J     -  Text Table for Intrastat Reports 
T160L    -  Scope of Purchasing Lists 
T160M   -  Message Control: Purchasing (System Messages) 
T160O   -  Description of Scope of List 
T160P    -  Entities Table Routines 
T160Q   -  Scope of List: Buyer's Negotiation Sheet: Routine
T160R   -  Routines for Buyer's Negotiation Sheet 
T160S   -  Selection Parameters for Purchasing Lists 
T160T   -  Description of Selection Parameters 
T160V   -  Default Values for Purchasing 
T160W  -  Description for Default Values for Purchasing Ope
T160X   -  Scope of List: Buyer's Negotiation Sheet 
T160Y   -  Scope of List: Buyer's Negotiation Sheet: Descrip
T161      -  Purchasing Document Types 
T161A   -  Linkage of Requisition Doc. Type to Purchasing Do
T161B   -  Default Business Transaction Type for Import 
T161E   -  Release Codes 
T161F   -  Release Point Assignment for Purchase Requisition
T161G   -  Release Prerequisite, Purchase Requisition 
T161H   -  Fields for Release Procedure, Purchase Requisitio
T161I    -  Determination of Release Strategy 
T161M  -  Fine-Tuned Control: Message Types 
T161N  -   Message Determination Schemas: Assignment 
T161P   -  Check of Document Type, Document Category, Item C
T161R   -  REORG Control, Purchasing 
T161S   -  Release Indicator, Purchase Requisition 
T161T   -  Texts for Purchasing Document Types 
T161U  -   Texts for Release Indicator 
T161V  -   Shipping-Specific Data for Stock Tfr. for Purch. 
T161W -   Order Types for Stock Transfer 
T161Z   -   Additional Checks for Outline Agreements on Reorg
T162     -   Field Selection, Purchasing Document 
T162K  -   Field Selection, Account Assignment Fields, Purch
T162T   -   Description of Field Selection Reference Key 
T162X   -   Description of Field Groups from T162/T162K 
T162Y   -   Groups: Field Selection 
T163      -   Item Categories in Purchasing Document 
T163A    -  Check Item Category/Account Assignment Category 
T163B    -  Purchase Order History Categories 
T163C   -   Texts for Purchase Order History Categories 
T163D   -   Assignment Internal/External Confirmation Categor
T163E   -   Confirmation Categories 
T163F    -  Confirmation Categories: Descriptions 
T163G   -  Confirmation Control 
T163I     -  Texts for Account Assignment Categories 
T163K   -  Account Assignment Categories in Purchasing Docum
T163KS -  Assignment of Tax Indicator to Account Assignment
T163L    -  Confirmation Control Keys 
T163M   -  Confirmation Control Keys: Description 
T163P    -   Release Creation Profile 
T163S    -  Description for Release Creation Profile 
T163X   -  "Zombie" T163X 
T163Y   -  Texts for Item Categories 
T165K   -  Copying Options: Header Texts 
T165P    -  Copying Options: Item texts 
T166A    -  Supplement Text in Purchasing Document Printouts 
T166C    -  Print-Relevant Purchasing Document Changes 
T166K    -  Header Texts in Purchasing Document Printouts 
T166P     -  Item Texts in Purchasing Document Printouts 
T166T     -   Change Texts in Purchasing Document Printouts 
T166U    -   Headings in Purchasing Document Printout 
T167       -   Number Range Management for Purchasing Master Dat 
T167T     -   Transaction Description 
T168       -   Screen Control, Purchasing 
T168F     -   Function Codes, Purchasing 
T168T     -  Screen Titles 
T16FB    -  Release Indicators: Purchasing Document 
T16FC    -  Release Codes 
T16FD    -  Description of Release Codes 
T16FE     -  Descriptions of Release Indicators: Purchasing Do 
T16FG    -   Release Groups 
T16FH    -   Descriptions of Release Groups 
T16FK    -   Release Statuses 
T16FS     -   Release Strategies 
reward POINTS if hlpful.

Similar Messages

  • SAP Tables for FI Accounts Payable

    Hello gurus,
    Does anyone know what are the SAP Tables for FI Accounts Payable and what TCodes to display these A/P tables?
    Thanks in advance.
    Best regards,
    Gab

    And use transaction code SE16 to view the tables mentioned by Jan.  And to add check BSAK for cleared items.
    Elias
    Edited by: Elias Akorli on Dec 11, 2009 4:01 PM
    Edited by: Elias Akorli on Dec 11, 2009 4:02 PM

  • Table relationship between Profit Center and G/L account.

    Hi,
    I have an issue related to wrong profit centers. We have a workflow that updating the profit center to a G/L account regarding the business of Reverse Logistic. In that business, we shift from a G/L account to another G/L account.
    Now I have to find the tables relationship between Profit center and G/L account, which contains the correct relationship between a profit center and a G/L account, so that I can profit centers related to the moved G/L account and the original G/L account.
    Thank you.
    Moderator: Please, search before posting

    Hi
    The Posted data can be seen in BSEG & GLPCA/FAGLFLEXA
    The default assignment of GL & PC can be seen in 3KEH / FAGL3KEH
    br, Ajay M

  • Sap report purchasing and accounts payable

    Dear gurus,
    I intend to create a vendor payment report that would create clarity on the operations in purchasing and accounts payable.
    Which tables would be idea to create such report?
    BR,
    Tolu

    (Only some of the most important tables)
    For MM purchasing, check
    - EKKO     Purchasing Document Header
    - EKPO     Purchasing Document Item
    - EKBE     History per Purchasing Document
    - EKKN     Account Assignment in Purchasing Document
    (Also look at logical database BRM, EBM, ECM, EKM, ELM, EMM, ENM, ERM, EWM,MEPOLDB, PSJ   definitions)
    For FI-AP financial account payable
    - BKPF     Accounting Document Header
    - BSEG     Accounting Document Segment
    - BSIK     Accounting: Secondary Index for Vendors
    - BSAK     Accounting: Secondary Index for Vendors (Cleared Items)
    - BSIS     Accounting: Secondary Index for G/L Accounts
    - BSAS     Accounting: Secondary Index for G/L Accounts (Cleared Items)
    - BSIM     Secondary Index, Documents for Material
    (Also look at logical database BMM, BRF, BRM, KDF definitions)
    Regards,
    Raymond

  • Fully Paid invoice is  appearing in "Accounts payable  trial balance"

    Hi all,
    i have proble with AP trial balance report..
    there is one invoice which is fully paid and accounted.
    but still that invoice is appearing in trial balance report.
    invoice amount is 0000000
    rmaing amount is (9856568) note: negatinve amoun..
    any one pls suggest as soon as possible
    thanx

    hi Octopus Rex ,
    rite.
    But i have one doubt tht.i have invoice which is paid.but it is still in "AP_LIABILITY_BALNCE" as you mentined **"The Accounts Payable Trial Balance report uses this information to report on outstanding invoice liability"**.But i have only single line for that paid invoice.
    the table "AP_LIABILITY_BALANCE" sholud have the oustanding amount only rite.why i am getting this paid invoice.
    can u give some point to releated paid invoce that will appear in this table

  • List of invoices paid in accounts payable with corresponding expense GL

    Hi,
    Need to know whether there ia any standard report in SAP ECC 6.0 version where we can get the list of all invoices paid  in a period  in A/Pwith corresponding expense GL Account. IF we need to build report painter report or query  any idea which tables will contain all these information. If any one is having functional specification document it will be of great help.
    Regards,
    Vipin

    Hi,
    - check in Easy Access->Accounting-> Fin Acctng->Accounts Payable-> Vendors:Items or Payment Transactions (like S_P99_41000099 or S_ALR_87012085 etc.,)
    - relevant tables would be BSAK or BSEG
    Rgds.

  • SRM 7.0 Add Fields in Account Assignment Table

    Hi SRM Gurus,
    I am working on SRM7.0.
    I want to add two fields in Account Assignment Table in Account assignment tab of Shopping cart Item.
    I can do it using WebDynpro Enhancement framework , i.e.
    1) Create an append structure for Structure INCL_EEW_PD_ACC_CSF
    2) Enhance WebDynpro Component : /SAPSRM/WDC_UI_DO_ACC - Component controller node
    3) Map this with View  V_DO_ACCOUNTING Node
    4) Create the necessary Table Columns and Column editors in Account Assignment Table
    However i think using SPRO configuration and enhancing few structures also this can be achieved.
    Can anyone guide me on how can i achieve it without creating WebDynpro ABAP Enhancement?
    Regards,
    Ashish Shah

    I've never done it with account data, but yes with header and item.
    I think in this case you need to add these fields in SPRO:
    SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Extensions and Field Control (Personalization) --> Configure Field Control --> Configure Control for Fields of Substructures --> Metadata for Fields of Substructures and Table-Like Enhancements
    Adding the fields with "Set Type" = 31 Accounting...

  • SRKIM: R12: Accounts Payable Trial Balance issue troubleshoot

    Purpose
    R12 에서 AP Trial Balance Report 확인 시 데이터가 비정상적일 경우 check 해야 하는 내용에 대해 확인 해 보도록 한다.
    Question
    R12 에서 invoice 생성 후 gl 로 transfer 하였으나 ap trial balance report 의 데이터가 비정상적인 것으로 확인 된다.
    어떤 내용을 확인 해야 하는가.
    Answer
    1. APList Diagnostics Script 을 해당 invoice 에 대해 수행 하여 아래의 내용을 확인한다.
    - Accounting 이 생성되어 gl로 모두 transfer 되었는지 여부.
    - Accounting Date 가 Trial Balance Report 의 start date 와 as of date 안에 포함 되는지 여부
    2.위의 내용에 문제가 없다면 아래 sql 로 데이터를 확인 해 보도록 한다.
    select *
    from xla_trial_balances
    where source_entity_id in (
    select entity_id
    from xla.xla_transaction_entities xte
    where application_id = 200
    and (
    (entity_code = 'AP_INVOICES' and source_id_int_1 in (&invoice_id))
    OR
    applied_to_entity_id in (
    select entity_id
    from xla.xla_transaction_entities xte
    where application_id = 200
    and (
    (entity_code = 'AP_INVOICES' and source_id_int_1 in (&invoice_id))
    3.GL 에 실제 해당 데이터가 존재 하는지 아래 sql 로 확인 해 보도록 한다.
    SELECT distinct aeh.*
    FROM gl_je_lines gjl, GL_IMPORT_REFERENCES gir, gl_je_headers gjh, GL_JE_BATCHES gjb, XLA_AE_LINES
    ael,
    XLA_AE_HEADERS aeh, XLA_EVENTS aea, xla.xla_transaction_entities xte
    WHERE ael.gl_sl_link_id = gir.gl_sl_link_id
    and gjh.je_batch_id= gjb.je_batch_id
    and gjl.je_header_id = gjh.je_header_id
    and gjl.je_header_id = gir.je_header_id
    and gjl.je_line_num = gir.je_line_num
    AND gir.gl_sl_link_table in ('XLAJEL')
    and ael.gl_sl_link_table in ('XLAJEL')
    AND aea.application_id = 200
    AND aea.event_id = aeh.event_id
    AND aeh.ae_header_id = ael.ae_header_id
    AND gjb.je_batch_id = gir.je_batch_id
    and xte.application_id = 200
    and xte.entity_id = aea.entity_id
    and gjh.je_header_id = gir.je_header_id
    and gjh.je_source = 'Payables'
    and (
    (xte.entity_code = 'AP_PAYMENTS' and xte.source_id_int_1 = &check_id)
    OR
    (xte.entity_code = 'AP_INVOICES' and xte.source_id_int_1 = &invoice_id)
    SELECT distinct gjl.*
    FROM gl_je_lines gjl, GL_IMPORT_REFERENCES gir, gl_je_headers gjh, GL_JE_BATCHES gjb, XLA_AE_LINES
    ael,
    XLA_AE_HEADERS aeh, XLA_EVENTS aea, xla.xla_transaction_entities xte
    WHERE ael.gl_sl_link_id = gir.gl_sl_link_id
    and gjh.je_batch_id= gjb.je_batch_id
    and gjl.je_header_id = gjh.je_header_id
    and gjl.je_header_id = gir.je_header_id
    and gjl.je_line_num = gir.je_line_num
    AND gir.gl_sl_link_table in ('XLAJEL')
    and ael.gl_sl_link_table in ('XLAJEL')
    AND aea.application_id = 200
    AND aea.event_id = aeh.event_id
    AND aeh.ae_header_id = ael.ae_header_id
    AND gjb.je_batch_id = gir.je_batch_id
    and xte.application_id = 200
    and xte.entity_id = aea.entity_id
    and gjh.je_header_id = gir.je_header_id
    and gjh.je_source = 'Payables'
    and (
    (xte.entity_code = 'AP_PAYMENTS' and xte.source_id_int_1 = &check_id)
    OR
    (xte.entity_code = 'AP_INVOICES' and xte.source_id_int_1 = &invoice_id)
    4.위의 sql 을 통해 Trial Balance Table 의 데이타가 잘 못 생성 되었음이 확인 되면 해당 Trial balance table 의 데이타를 recreate 하는 작업을 수행 해야 한다.
    Reference
    Note. 553484.1 - THE R12 ACCOUNTS PAYABLE TRIAL BALANCE DATA IS
    INCORRECT/WRONG

    Follow the below steps and Run the Trial Blance and let me know if it helps.
    Thanks
    Girish
    How to Rebuild Trial Balance Data (repopulate XLA_TRIAL_BALANCES)
    1. Navigate: Payables Responsibility > Setup > Accounting Setups > Subledger Accounting Setups > Open Account Balances Listing Definitions
    2. Query up your Report Definition: select Defined By = Accounting Flexfield or Segment (whichever applies in your case), click “Go”
    3. Click on Update icon in the "Actions" column – the definition's update page opens.
    4. "Touch" the definition by simply clicking "Apply" button (without making any change).
    This should start the “Open Account Balances Data Manager” concurrent processes

  • Data Flow Purchasing - Accounts Payable

    Dear Experts,
    I would like to understand the relationship between purchasing and accounts payable. Can you tell me the data flow explaining the relationship? Can you tell me what I should know from a BW reporting perspective?
    Thanks,
    Karthik

    Hi,
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
    Hope this helps,
    regards
    CSM Reddy

  • Accounts Payable Stuff

    Hi Experts,
    I am new to this Financials. Can any body give me the stuff related to Accounts payable from the beginning means,
    from what is Accounts payable to what are the Tcodes and related tables we work on.
    Thanks in Advance.
    Siddik.

    Hello Siddik,
    Refer the following SAP Help link which gives complete details about the Finance- Accounts Payable(FI-AP) --
    http://help.sap.com/saphelp_47x200/helpdata/en/a4/be8e3c2
    936230ae10000000a114084/content.htm
    PS Reward points to everyone responding if the answer helps you.
    Regards

  • Accounts payable master data

    Hi All
    Cud any one provide sample code how to upload accounts payable master data?
    thnx in advance,
    Pavani.

    Hi
    Account Payables means the amounts that are to be paid to vendor against the purchase we made
    So here the master data menas the VENDOR, MATERIAL data
    see the related BDC programs
    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.
    REPORT zmm_vendor_master_upload
           NO STANDARD PAGE HEADING
           LINE-SIZE 255.
    ABAP Name   :   ZMM_VENDOR_MASTER_UPLOAD
    Description :   This Program is used to Upload the Vendor Master.
    Standard Include for Selection Screen
    INCLUDE bdcrecx1.
    Internal Table for Upload Data
    DATA: BEGIN OF i_vendor OCCURS 0,
            bukrs(004),             " Company Code
            ekorg(004),             " Purchase Orgn
            ktokk(004),             " Account Group
    Address Screen
            anred(015),             " Title
            name1(035),                                         " Name1
            sortl(010),             " Sort Field
            name2(035),                                         " Name2
            name3(035),             " Contact Person1
            name4(035),             " Contact Person 2
            stras(035),             " Street
            pfach(010),             " PO Box
            ort01(035),             " City
            pstlz(010),             " Postal Code
            land1(003),             " Country
            spras(002),             " Language
            telf1(016),             " Telephone No
            telfx(031),             " Fax Number
            lfurl(132),             " URL-Mail Id
    Material Group Characteristics
           klart(003),             " Class Type '010'
           class(018),             " Class 'Vendor'
           mname_01(030),          " Characteristic
           mname_02(030),          " Characteristic
           mname_03(030),          " Characteristic
            mwert_01(030),          " Charct.Value
            mwert_02(030),          " Charct.Value
            mwert_03(030),          " Charct.Value
    Control Data
            emnfr(010),             " Manufact.Part No
    Bank Details
            banks_01(003),          " Country of Bank1
            banks_02(003),          " Country of Bank2
            bankl_01(015),          " Bank Key of 1
            bankl_02(015),          " Bank Key of 2
            bankn_01(018),          " Account No Bank1
            bankn_02(018),          " Account No Bank2
    Accounting Info
            akont(010),             " Reconcillation Account
            zuawa(003),             " Sort Key
            fdgrv(010),             " Cash Management Group
    Payment Transactions
            zterm(004),             " Payment terms
           reprf(001),             " Check Double Inv.
            zwels(010),             " Payment Method
            hbkid(005),             " House Bank
           xpore(001),             " Individ.Payment
    Correspondence
            mahns(001),             " Dunning Level
            xausz(001),             " Account Statement
    Withholding Tax Details
            qland(003),             " Withholding Tax Country
            witht_01(002),          " WH tax Type
           wt_withcd(002),        " WH Tax Code
           wt_subjct(001),        " Indicator:WH Tax
    Purchasing Data
            waers(005),             " Currency
            zterm1(004),            " Payment Terms
          END OF i_vendor.
    Data Variables & Constants
    CONSTANTS : c_x     VALUE 'X'.  " Flag
    Paramters
    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_vendor
        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_vendor.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0100'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RF02K-KTOKK'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'RF02K-BUKRS'
                                      i_vendor-bukrs.
        PERFORM bdc_field       USING 'RF02K-EKORG'
                                      i_vendor-ekorg.
        PERFORM bdc_field       USING 'RF02K-KTOKK'
                                      i_vendor-ktokk.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0110'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFA1-SPRAS'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=KLAS'.
        PERFORM bdc_field       USING 'LFA1-ANRED'
                                      i_vendor-anred.
        PERFORM bdc_field       USING 'LFA1-NAME1'
                                      i_vendor-name1.
        PERFORM bdc_field       USING 'LFA1-SORTL'
                                      i_vendor-sortl.
        PERFORM bdc_field       USING 'LFA1-NAME2'
                                      i_vendor-name2.
        PERFORM bdc_field       USING 'LFA1-NAME3'
                                      i_vendor-name3.
        PERFORM bdc_field       USING 'LFA1-NAME4'
                                      i_vendor-name4.
        PERFORM bdc_field       USING 'LFA1-STRAS'
                                      i_vendor-stras.
        PERFORM bdc_field       USING 'LFA1-PFACH'
                                      i_vendor-pfach.
        PERFORM bdc_field       USING 'LFA1-ORT01'
                                      i_vendor-ort01.
        PERFORM bdc_field       USING 'LFA1-PSTLZ'
                                      i_vendor-pstlz.
        PERFORM bdc_field       USING 'LFA1-LAND1'
                                      i_vendor-land1.
        PERFORM bdc_field       USING 'LFA1-SPRAS'
                                      i_vendor-spras.
        PERFORM bdc_field       USING 'LFA1-TELF1'
                                      i_vendor-telf1.
        PERFORM bdc_field       USING 'LFA1-TELFX'
                                      i_vendor-telfx.
        PERFORM bdc_field       USING 'LFA1-LFURL'
                                      i_vendor-lfurl.
        PERFORM bdc_dynpro      USING 'SAPLCLCA' '0602'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMCLF-KLART'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ENTE'.
        PERFORM bdc_field       USING 'RMCLF-KLART'
                                      '010'. "i_vendor-klart.
        PERFORM bdc_dynpro      USING 'SAPLCLFM' '0500'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMCLF-CLASS(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=AUSW'.
        PERFORM bdc_field       USING 'RMCLF-CLASS(01)'
                                      'Vendor'."i_vendor-class.
        PERFORM bdc_dynpro      USING 'SAPLCTMS' '0109'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RCTMS-MWERT(03)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=BACK'.
        PERFORM bdc_field       USING 'RCTMS-MNAME(01)'
                           'MATERIALGROUP'." i_vendor-mname_01.
        PERFORM bdc_field       USING 'RCTMS-MNAME(02)'
                           'MATERIALGROUP'." i_vendor-mname_02.
        PERFORM bdc_field       USING 'RCTMS-MNAME(03)'
                           'MATERIALGROUP'." i_vendor-mname_03.
        PERFORM bdc_field       USING 'RCTMS-MWERT(01)'
                                      i_vendor-mwert_01.
        PERFORM bdc_field       USING 'RCTMS-MWERT(02)'
                                      i_vendor-mwert_02.
        PERFORM bdc_field       USING 'RCTMS-MWERT(03)'
                                      i_vendor-mwert_03.
        PERFORM bdc_dynpro      USING 'SAPLCLFM' '0500'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMCLF-CLASS(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ENDE'.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0110'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFA1-ANRED'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0120'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFA1-EMNFR'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFA1-EMNFR'
                                      i_vendor-emnfr.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0130'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFBK-BANKN(02)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                          '=VW'.
        PERFORM bdc_field       USING 'LFBK-BANKS(01)'
                                      i_vendor-banks_01.
        PERFORM bdc_field       USING 'LFBK-BANKS(02)'
                                      i_vendor-banks_02.
        PERFORM bdc_field       USING 'LFBK-BANKL(01)'
                                      i_vendor-bankl_01.
        PERFORM bdc_field       USING 'LFBK-BANKL(02)'
                                      i_vendor-bankl_02.
        PERFORM bdc_field       USING 'LFBK-BANKN(01)'
                                      i_vendor-bankn_01.
        PERFORM bdc_field       USING 'LFBK-BANKN(02)'
                                      i_vendor-bankn_02.
       PERFORM bdc_dynpro      USING 'SAPMF02K' '0130'.
       PERFORM bdc_field       USING 'BDC_CURSOR'
                                     'LFBK-BANKS(01)'.
       PERFORM bdc_field       USING 'BDC_OKCODE'
                                     '=VW'.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0210'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFB1-FDGRV'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFB1-AKONT'
                                      i_vendor-akont.
        PERFORM bdc_field       USING 'LFB1-ZUAWA'
                                      i_vendor-zuawa.
        PERFORM bdc_field       USING 'LFB1-FDGRV'
                                      i_vendor-fdgrv.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0215'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFB1-XPORE'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFB1-ZTERM'
                                      i_vendor-zterm.
        PERFORM bdc_field       USING 'LFB1-REPRF'
                                      c_x. "i_vendor-reprf.
        PERFORM bdc_field       USING 'LFB1-ZWELS'
                                      i_vendor-zwels.
        PERFORM bdc_field       USING 'LFB1-HBKID'
                                      i_vendor-hbkid.
        PERFORM bdc_field       USING 'LFB1-XPORE'
                                      c_x. "i_vendor-xpore.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0220'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFB5-MAHNS'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFB5-MAHNS'
                                      i_vendor-mahns.
        PERFORM bdc_field       USING 'LFB1-XAUSZ'
                                      i_vendor-xausz.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0610'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFBW-WT_SUBJCT(01)'.
        PERFORM bdc_field       USING 'LFB1-QLAND'
                                      i_vendor-qland.
        PERFORM bdc_field       USING 'LFBW-WITHT(01)'
                                      i_vendor-witht_01.
       PERFORM bdc_field       USING 'LFBW-WT_WITHCD(01)'
                                     i_vendor-wt_withcd.
        PERFORM bdc_field       USING 'LFBW-WT_SUBJCT(01)'
                                       c_x.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0310'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'LFM1-ZTERM'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_field       USING 'LFM1-WAERS'
                                      i_vendor-waers.
        PERFORM bdc_field       USING 'LFM1-ZTERM'
                                      i_vendor-zterm1.
        PERFORM bdc_dynpro      USING 'SAPMF02K' '0320'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RF02K-LIFNR'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=VW'.
        PERFORM bdc_dynpro      USING 'SAPLSPO1' '0300'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=YES'.
    Call the Transaction
        PERFORM bdc_transaction USING 'XK01'.
      ENDLOOP.
    Close the BDc Session
      PERFORM close_group.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Accounts payable using ADI

    Hi everyone,
    i recently read that it is possible to create accounts payable from ADI.
    i knew that it was possible for creating assets, journal entries and budgets.
    i think if this really works this would alleviate the burden of entering invoices
    directly to oracle AP since the same invoices may be already available in the form of a spreadsheet.
    this will mean time savings and the lesser the probability to make errors to the wrong supplier with the wrong amounts.
    could someone tell me how to make the above a reality as tried but found nothing.
    thanks

    No. ADI is available for GL and FA. You can use a tool called SQLXL to connect from excel spreadsheet to "Oracle AP Open Interface Tables" and run payables open interface program to create invoices. If you are an expert in excel macros, this is feasible.

  • Accounts Payable Query

    Dear All,
             I am analysing data which goes through 0fi_ap_4 data source. I seek info on how accounts payable data is distinguished from General Ledger data.Since accounts payable is a subset of general ledger data, from which table does 0fi_ap_4 take info from and what is the field used to decide that a certain records is related to accounts payable?
    Regards,
    Ratish
    [email protected]
    Edited by: Ratish Premachandran on Jan 18, 2008 12:22 PM

    Hi,
    Check the ppt file.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
    Regards.

  • Accounts Payable Aging

    Dear All,
             I am in need to develop customized report on Vendor Accounts payable - Aging for given slab.
    I can find the open items for the given key date in the table BSIK.
             if we want to calculate due on past date( for cleared item), how can we use BSIK. ?        
            Let consider the following scenario.
                  Consider an item is cleared on 10.02.2009.   if the key date is 18.05.2009, there is no due for this item. But if the keydate is 15.12.2008, the item is on due. (consider 15.12.2008 is calculated with baseline date, credit days).
             How can we calculate aging for this from BSIK. because BSIK contains only open items.
    If we use BSAK ( Cleared Items ). How to calculate aging using baseline date, clearing date, credit days.
    Regards,
    S.Sridhar

    To calculate aging,
    You com use the FM J_1B_FI_NETDUE. If i undestand your problem, that FM will help you to calculate aging.
    Regards

  • Document in Accounts Payable

    Hi Experts,
    I am new to FI and need some help. I am seeing that some of the incoive receipts(documtn type RE) which I can se BKPF & FB03 are not in accounts payable. What are the scenarios where an invoice document will not appear in accounts payable?. Could you plese give me some details?.
    Also, s detailed document for a beginner in FI will be very helpful!!
    Regards,
    Shilpa

    BSEG is a cluster table in SAP. It is comprised of few transparent  tables like BSIS, BSAS, BSIK, BSAK, BSID, BSAD, BSIP and couple more.
    You will see all documents  in BSEG. but  these documents might be broken down in other tables.
    Check your document number in BSIS and BSAS tables. It should be there but credits and debits might be divided.
    Also, BSIK, BSAK have line items that have vendor number reference.
    Thanks,
    Preeti

Maybe you are looking for