Invoice rfc

hi pals,
I have to do one dummy scenario, I have created the all the information such as company information, product information, release of the SAP Business System , namespace, etc.
Now the integration scenario is – <b>IS_PurchaseOrderGetDetails</b>
the data types is created and such as DT_PurchaseOrder_Req and response.
Message Type MT_PurchaseOrder_Req and that of response also.
mesage interface and mapping interface mapping is also done.
now i have to get the details of the invoice as a response when a request is given.
what is the BAPI to be used..
please give the steps to be taken.
please do help me in solving...this is my first task..
will be thankful for all the help..
regards
AK

Hi,
use : BAPI_INCOMINGINVOICE_GETDETAIL
to get details from an invoice
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Similar Messages

  • Mesage interfaces...

    hi pals,
    While creating an Invoice RFC i came across message type creation.
    After that create message interface
    what is actually
    <b>1. Message interface file request
    2. Abstract interface File request
    3.Message interface file response
    4. Abstract interface File response.
    </b>
    regards
    A.K.

    Hi,
    1. Message interface file request
    This is use , a interface using file request which is equalent msg structure to the RFC request , you are trying to send the request to the RFC request
    2. Abstract interface File request
    This is use , a interface using file abstract request which is equalent msg structure to the RFC request in Integration process , you are trying to send the request to the RFC request from Integration process.
    3.Message interface file response
    This is use , a interface using file response which is equalent msg structure to the RFC response , you are trying to receive the response from the RFC response
    4. Abstract interface File response
    This is use , a interface using file abstract response which is equalent msg structure to the RFC response in Integration process, you are trying to receive the response from the RFC response
    See the below Link
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    Regards
    Chilla..

  • BAPI or RFC to simulate an FI invoice creation

    Hi,
    I need to develop an RFC or BAPI that acts as the SIMULATE function of the transaction FB01 (invoice creation).
    Could you recommend any tips (es. standard BAPI, Function Modules, etc.) ?
    Thank you very much in advance.
    Best Regards.
    Mauro

    I thank you very much for your tips.
    Unfortunately, recommended standard BAPIs are not suitable for me.
    I need something to be called from remote/RFC that returns the "structure" displayed on the screen when you select the SIMULATE option of the FB01 transaction.
    I tried with a Batch Recording, but I do not find in which data structure the system put the data (it seems that the Module Pool displays the data on the screen and then delete the data structure, without returning it to the batch recording).
    I thank you very much.
    Mauro

  • Error in Process u2013 PO cannot be reduced to the value already invoiced.

    Hi,
    i need some idea abt this.
    the requirement is provide an error message when ordered qty and price is lower than invoiced qty and price and PO cannot be changed.
    A New RFC is required to fetch the values of Invoiced Quantity and Invoiced Amount taking Purchase Order Number as input. In order to make it simpler, make use of logic available in FMu2019s BBP_PO_GETDETAIL and BBP_PO_GETITEMS else use the same FM inside the RFC.
    At first, check whether the PO is a Service or Goods PO. Call the RFC inside the BAdi at PO level and pass the PO Number. The RFC will then return you with Invoiced Quantity and Invoiced Amount.
    Validate this Invoiced Qty and Amt with current values user has entered. If ordered qty and amt is lower than invoiced qty and amt, error should be created and PO cannot be changed.
    Can anyone suggest how i should approach regarding this issue.
    Thanks in Advance.

    Hi ,
      Find out exact user-exit or BADI for the solution.
    Thanks,
    Archana.

  • Look up account assignment via BAPI/RFC

    Hello,
    I would like to look up Account Assignment data from an external application to post the a similar invoice every month using the bapi BAPI_INCOMINGINVOICE_CREATE. I cannot find a RFC FM or BAPI available. Can someone suggest an example FM or method so I can retrieve this information? Which tables are used?
    Thanks,
    Aaron

    HI,
    Try to find some enhancement for BAPI_INCOMINGINVOICE_CREATE1 to achieve your requirement.
    Regards,
    Sid

  • Tables for vendor invoice and payment

    Hi Gurus.
    I want to know from which tables i can get the information for folllowing points.
    1.       Vendor Invoices  - Complete (Header and Item)
    2.       Vendor Payments Details – Detail about payment method (check, wire, etc)
    Please tell me tje table names.

    There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
    |Table Name               |Table Description                                           |
    |/BEV3/CHKOMPAZVV         |Append Structure CH -> CO PA                                |
    |/CWM/ACCIT               |Append Structure for Enhancement of Structure ACCIT in CWM  |
    |/CWM/KOMP                |Catch Weight Management Enhancement                         |
    |/DSD/TAXJURCD            |Ship From Tax Jurisdiction Code: for Header Prc Comm Str    |
    |/SAPNEA/J_SC_LFA1        |Subcontractor Information                                   |
    |/SAPNEA/J_SC_LFB1        |Subcontracting Management                                   |
    |/SAPPSPRO/A_FI2_LONGNUM  |IBU-PS:  Append structure for structure NONBSEG             |
    |/SAPPSPRO/A_LONGNUMBER   |additional fields for SPIIN number                          |
    |/SAPPSPRO/EADD           |Purchasing Document Header: Additional Data                 |
    |/SAPPSPRO/EADD_DATA      |Purchasing Document Header: Data Part Additional Information|
    |/VSO/R_KNA1_A            |Append to KNA1 for Vehicle Space Optimization               |
    |/VSO/R_KNA1_I            |Additional Data for Vehicle Space Optimization for KNA1     |
    |AACCHD_FMFG              |US federal fields                                           |
    |AACCHD_PSO               |IS-PS: ACCHD Append Structure for Payment Requests          |
    |AACCIT_GM                |Append for Grants Management                                |
    |AACCIT_PSO               |IS-PS: ACCIT Append Structure for Payment Requests          |
    |AACCIT_SSP               |Append for Payment Statistical Sampling Process             |
    |AACCIT_USFG              |Append structure for US federal government                  |
    |AAUSZ_CLR_USFG           |Clearing information for US Fed (Tresury Confirmation)      |
    |ABKPF_PSO                |IS-PS: BKPF Append Structure for Payment Requests           |
    |ABKPF_UMB                |IS-PS: Append Structure for Transfer Transaction FMITPO     |
    |ABSID_PSO                |IS-PS: Data appendix of open items customers                |
    |ABSIK_PSO                |IS-PS: Data appendix of open items vendors                  |
    |ABSIS_PSO                |Local Authorities                                           |
    |ABUZ                     |Help Structure for Line Items to be Generated Automatically |
    |ACCCR                    |Accounting Interface: Currency Information                  |
    |ACCCR_FKEY               |Key: Acctg Currency Data for Line Item Including Currency   |
    |ACCCR_KEY                |Key: Accounting Currency Data for Line Item                 |
    |ACCFI                    |Interface to Accounting: Financial Acctg One-Time Accts     |
    |ACCHD                    |Interface to Accounting: Header Information                 |
    |ACCHD_KEY                |Key: FI/CO Document Header                                  |
    |ACCIT                    |Accounting Interface: Item Information                      |
    |ACCIT_EXTENSION          |ACC Document: Additional Item Information                   |
    |ACCIT_JV                 |Joint Venture Accounting                                    |
    |ACCIT_KEY                |Key: FI/CO Line Item                                        |
    |ACCIT_WT                 |Withholding tax information for FI Interface                |
    |ACCRDF                   |Fields for Posting Small Differences: Preparation           |
    |ACC_DOCUMENT             |Accounting document                                         |
    |ACC_KONTEXT              |Context Info for FI Single Screen Transactions FB50 and FB60|
    |ACERRLOG                 |Return Parameter                                            |
    |ACGL_HEAD                |Fields for Document Header Entry Screen                     |
    |ACGL_ITEM                |Structure for Table Control: G/L Account Entry              |
    |ACSCR                    |Communication Structure for Field Modification SAPLFDCB     |
    |ACSPLT                   |Carrier for Split Information re: Current Account Line Items|
    |ACSPLT_WTNEW             |Proportion of New Withholding Tax                           |
    |ACSPLT_WTOLD             |Proportion of Old Withholding Tax                           |
    |ADDR1_SEL                |Address selection parameter                                 |
    |AEBPP_KNBK               |Additional Fields Bank Data Biller Direct                   |
    |AEBPP_LFBK               |Additional Fields Bank Data Biller Direct                   |
    |AFMIOI                   |Append for new fields ECC50/ERP                             |
    |AFMIOI_USFG              | SD order needs quantity                                    |
    |AFMISPS                  |Additional Fields for Table FMISPS                          |
    |AFM_ACCIT_EXTENSION      |Extension for FM Payment Update                             |
    |AFM_FAGL_GLT0_ACCIT_EXT  |Extension FM Account Assignments                            |
    |AFM_FI_BKPF_SUBST        |Append to Structure BKPF_SUBST                              |
    |AFM_FMFCTF               |Append for Fund Center substrings                           |
    |AFM_FMFINCODE            |Append for Fund substrings                                  |
    |AIFM01D                  |Append for IFM01D                                           |
    |AKNA1_FMFG               |US Federal Government Customer Master Data Additional Fields|
    |AKNA1_PSO                |Local Authority Additional Fields                           |
    |AKNB1_PSO                |IS-PS: Customer Master Record, Additional Data (Co.Code)    |
    |AKNBK_PSO                |Bank Details Dependent on Time and Account Holder           |
    |ALFA1_FMFG               |US Federal Government Vendor Master Data Additional Fields  |
    |ALFA1_PSO                |Local Authority Additional Fields (Address)                 |
    |ALFB1_FMFG               |PS fields for company code-specific master data field       |
    |ALFB1_PSO                |IS-PS: Data Appendix Vendor Master Record (Company Code)    |
    |ALFBK_PSO                |Bank Details Dependent on Time and Account Holder           |
    |ALVDYNP                  |ALV dialog screen fields                                    |
    |ALV_S_FCAT               |Field Catalog (for LVC and for KKBLO)                       |
    |ALV_S_FILT               |Filter Criteria (for LVC and for KKBLO)                     |
    |ALV_S_GRPL               |Group Levels (for LVC and for KKBLO)                        |
    |ALV_S_LAYO               |Layout (for LVC and for KKBLO)                              |
    |ALV_S_PCTL               |Structure for Checking Print in ALV                         |
    |ALV_S_PRNT               |Print settings (for LVC and KKBLO)                          |
    |ALV_S_QINF               |Structure for Quickinfos of Exceptions                      |
    |ALV_S_SGRP               |Field Groups (for LVC and for KKBLO)                        |
    |ALV_S_SORT               |Sort Criteria (for LVC and for KKBLO)                       |
    |ANBZ                     |Help structure for asset line item                          |
    |ANLZACCOUNT              |Additional Account Assignment Objects in Asset Accounting   |
    |ANLZACCOUNT_FKBER        |Account Assignment Objects: ANLZACCOUNT with Function Added |
    |ARC_PARAMS               |ImageLink structure                                         |
    |AT003_XBLNR2             |Append structure for US federal government                  |
    |AUSZ1                    |Clearing Table 1                                            |
    |AUSZ2                    |Clearing Table 2                                            |
    |AUSZ_CLR                 |Assign Clearing Item to Cleared Items                       |
    |AUSZ_CLR_ASGMT           |Assgt of Clrg Items - Cleared Items with Acct Assignment    |
    |AUSZ_INFO                |Open item data for clearing transactions                    |
    |AVBKPF_FMFG              |US federal                                                  |
    |AVBKPF_PSO               |IS-PS: Append Structure VBKPF for Payment Requests          |
    |AVBSEGDPSO               |IS-PS: Append Structure VBSEGD for Payment Requests         |
    |AVBSEGKPSO               |IS-PS: Append Structure VBSEGK for Payment Requests         |
    |AVIK                     |Payment Advice Header                                       |
    |AVIP                     |Payment Advice Line Item                                    |
    |BALHDR                   |Application log: log header                                 |
    |BALMT                    |Application Log: Structure for a formatted message          |
    |BAL_S_CLBK               |Application Log: Return routine definition                  |
    |BAL_S_CONT               |Application Log: Context                                    |
    |BAL_S_MSG                |Application Log: Message Data                               |
    |BAL_S_PAR                |Application Log: Parameter Name and Value                   |
    |BAL_S_PARM               |Application log: Parameters                                 |
    |BAPIASCONT               |Business Document Service: File Content ASCII               |
    |BAPIBDS01                |Business Document Service: Reference Structure for BAPIs    |
    |BAPICOMFIL               |BDS: Command File for Transport Entries                     |
    |BAPICOMPO2               |SBDS: Enhanced Component Information                        |
    |BAPICOMPO3               |SBDS: Enhanced Component Information                        |
    |BAPICOMPON               |Business Document Service: Component Table                  |
    |BAPICONNEC               |BDS: Structure for BDS Links                                |
    |BAPICONTEN               |Business Document Service: File Content                     |
    |BAPIDPROPT               |BDS: Structure for Properties                               |
    |BAPIFILES                |Business Document Services: Transfer Table for File Names   |
    |BAPIPROPER               |BDS: Structure for Properties                               |
    |BAPIPROPTL               |BDS: Structure for KPRO Properties                          |
    |BAPIQUERY                |BDS Structure for Query Table                               |
    |BAPIRELAT                |Business Document Service: Relations                        |
    |BAPIRET1                 |Return Parameter                                            |
    |BAPIRETURN               |Return Parameter                                            |
    |BAPISIGNAT               |Business Document Service: Signature Table                  |
    |BAPISRELAT               |Business Document Service: Relationship Table with Signature|
    |BAPIURI                  |Business Document Service: URI Table                        |
    |BDCMSGCOLL               |Collecting messages in the SAP System                       |
    |BDCRUN                   |Batch input: Runtime analysis                               |
    |BDIDOCSTAT               |ALE IDoc status (subset of all IDoc status fields)          |
    |BDI_SER                  |Serialization objects for one/several IDocs                 |
    |BDN_FKT                  |Business Document Navigator: Functions to be Excluded       |
    |BDWFAP_PAR               |Parameters for application function module - IDoc inbound   |
    |BDWFRETVAR               |Assignment of IDoc or document no. to method parameter      |
    |BDWF_PARAM               |Parameters for workflow methods for IDoc inbound processing |
    |BKDF                     |Document Header Supplement for Recurring Entry              |
    |BKDF_SUBST               |Process Interfaces: Substitutable fields during posting     |
    |BKORM                    |Accounting Correspondence Requests                          |
    |BKP1                     |Document Header Supplement for Update                       |
    |BKPF                     |Accounting Document Header                                  |
    |BKPFBU_ALV               |Document Overview: Display Document Headers in ALV Grid Ctrl|
    |BKPF_CARD                |Credit Card: Append for BKPF                                |
    |BKPF_LINE                |Item Category for XBKPF_TAB                                 |
    |BKPF_SUBST               |Process Interfaces: Substitutable Fields During Posting     |
    |BKPF_USFED               |Append structure for US federal government                  |
    |BLNTAB                   |Document Number Table for Financial Accounting              |
    |BNKA                     |Bank master record                                          |
    |BNKAAPP                  |Appendix to Table BNKA                                      |
    |BNKT                     |Conversion of temporary to internal bank keys               |
    |BOOLE                    |Boolean variable                                            |
    |BSEC                     |One-Time Account Data Document Segment                      |
    |BSEC_LINE                |Item Category for XBSEC_TAB                                 |
    |BSED                     |Bill of Exchange Fields Document Segment                    |
    |BSEE                     |Changeable Fields in the Line Item                          |
    |BSEG                     |Accounting Document Segment                                 |
    |BSEGL                    |Document Segment: Fields Derived for Line Layout Variant    |
    |BSEGS                    |G/L Item Transfer Structure for Single Screen Transactions  |
    |BSEGT                    |Transfer Table for the Tax Postings to be Generated         |
    |BSEGZ                    |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
    |BSEG_ALV                 |Document Overview: Document Item Display in ALV Grid Control|
    |BSEG_LINE                |Item Category for XBSEG_TAB                                 |
    |BSEG_SUBST               |Process Interfaces: Substitutable Fields During Posting     |
    |BSET                     |Tax Data Document Segment                                   |
    |BSEU                     |Line Item Additional Information (Update)                   |
    |BSEZ                     |Line Item Additional Information (Online)                   |
    |BSEZ_LINE                |Line Item Category for XBSEZ_TAB                            |
    |BSID                     |Accounting: Secondary Index for Customers                   |
    |BSIK                     |Accounting: Secondary Index for Vendors                     |
    |BSIP                     |Index for Vendor Validation of Double Documents             |
    |BSIS                     |Accounting: Secondary Index for G/L Accounts                |
    |BSIX                     |Index table for customer bills of exchange used             |
    |BTXKDF                   |Fields for Exch.Rate Difference Posting for Taxes           |
    |BVOR                     |Intercompany posting procedures                             |
    |CACS_A_CRM_SALES_COND    |Additional CRM Fields (Construction) From Sales Order Area  |
    |CACS_A_CUST_COND         |Commissions: Customer Fields Condition Technique            |
    |CACS_A_FIELDSPRICING     |Append for Condition Technique Fields from Commission System|
    |CACS_S_CRM_SALES_COND    |Additional CRM Fields (Construction) From Sales Order Area  |
    |CACS_S_CUST_COND         |Condition Attributes                                        |
    |CACS_S_FIELDSPRICING     |Comm.: All Condition Technique-Relevant Commission Fields   |
    |CACS_S_FSINS             |Customer Fields for Condition Technique of Insurances       |
    |CCDATA                   |Payment cards: Database fields relevant to both SD and FI   |
    |CFW_LINK                 |CFW: Link Info of a Container                               |
    |CI_COBL                  |Extension                                                   |
    |CKI_ACCIT_ML             |Transfer from MM to ML in accit-structure                   |
    |CNTLSTRLIS               |Control stream list                                         |
    |COBK                     |CO Object: Document Header                                  |
    |COBK_ONLY                |Non-key fields only in COBK (INCLUDE structure)             |
    |COBL                     |Coding Block                                                |
    |COBLF                    |Coding block: Tax table structure                           |
    |COBL_COKZ                |Assignment types for CO account assignments                 |
    |COBL_DB_INCLUDE          |Include with Additional Account Assignments for DB Tables   |
    |COBL_EX                  |Coding Block for External Applications (Not CO/FI)          |
    |COBL_FI                  |Fields from COBL that Must not Be Overwritten in FI         |
    |COBL_FM                  |Additional Fields for FM                                    |
    |D010SINF                 |Generated Table for View D010SINF                           |
    |D020S                    |System table D020S (screen sources)                         |
    |D020T                    |Screen Short Description                                    |
    |DBSEG                    |Dialog Supplementation BSEG (Taxes)                         |
    |DD02L                    |SAP Tables                                                  |
    |DD03P                    |Structure                                                   |
    |DD03V                    |Table fields view                                           |
    |DD07V                    |Generated Table for View DD07V                              |
    |DD23L                    |Matchcode ID                                                |
    |DD32P                    |Interface structure for search help parameters              |
    |DDSHDEFLT                |Description of a default value for search help fields       |
    |DDSHDESCR                |Interface: elementary search helps of a search help         |
    |DDSHFPROP                |Characteristics of search help parameters                   |
    |DDSHIFACE                |Interface description of a F4 help method                   |
    |DDSHRETVAL               |Interface Structure Search Help <-> Help System             |
    |DDSHSELOPT               |Selection options for value selection with search help      |
    |DDSUX030L                |Nametab Header, Database Structure DDNTT                    |
    |DDSUX031L                |Nametab Structure, Database Structure DDNTF                 |
    |DDTYPES                  |Table of all Dictionary types and classes                   |
    |DFIES                    |DD Interface: Table Fields for DDIF_FIELDINFO_GET           |
    |DISVARIANT               |Layout (External Use)                                       |
    |DOKHL                    |Documentation: Headers                                      |
    |DPPROPS                  |General property structure for data provider                |
    |DTC_S_LAYO               |Structure for Design of Double Table Control                |
    |DTC_S_TC                 |Structure for table controls in the double table dialog box |
    |DTC_S_TS                 |Tab Title Structure                                         |
    |DYNPREAD                 |Fields of the current screen (with values)                  |
    |E071                     |Change & Transport System: Object Entries of Requests/Tasks |
    |E071K                    |Change & Transport System: Key Entries of Requests/Tasks    |
    |EAPS_20                  |Field Enhancements for EA-PS 2.0                            |
    |EDIDC                    |Control record (IDoc)                                       |
    |EDIDS                    |Status Record (IDoc)                                        |
    |EDIFCT                   |IDoc: Assignment of FM to log. message and IDoc type        |
    |EDIMESSAGE               |Transfer Structure with all Sy Fields for T100              |
    |EDI_DS                   |Status record for interface to EDI subsystem                |
    |EDI_HELP                 |Help Structure for Reference Fields in EDI Function Groups  |
    |EK05A                    |Communication Area Purchasing - Financial Accounting        |
    |ESKN                     |Account Assignment in Service Package                       |
    |EUDB                     |Development Environment Objects                             |
    |EUOBJ                    |Workbench: Development Objects                              |
    |EXCLTAB_LINE             |Lines of EXCLTAB with OK Code to be Deactivated             |
    |EXISTING_DOC             |Original Document                                           |
    |F05ACTRL                 |Control Fields for SAPMF05A and Subprograms                 |
    |FAGLBSEGL_S              |Additional Sender Flds from General Ledger for Doc. Overview|
    |FAGL_GLT0_ACCIT_EXT      |Line Information for Document Splitting                     |
    |FAGL_MIG_S_BUKRS_LEDGER  |Combination of Company Code and Assigned Ledgers            |
    |FAGL_SPLIT_FLD_S         |Characteristics Permitted for Split                         |
    |FAGL_S_APPLICATION       |Application and Subapplication                              |
    |FAGL_S_BALDIM            |G/L Characteristics of Document Split in New General Ledger |
    |FAGL_S_BUKRS             |Structure with Company Code                                 |
    |FAGL_S_BUKRS_EXT         |Structure: Company Codes --> Ledgers                        |
    |FAGL_S_CURTYPES          |Currency Types of a Ledger                                  |
    |FAGL_S_MIG_001           |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S           |
    |FAGL_S_MIG_MGPLN_EXT     |Structure: Extended Migration Plan Information              |
    |FAGL_S_T8G40_BS          |Split Fields with Characteristic "Balance Sheet"            |
    |FCRD_VBKPF               |Credit Card: Include for Appends for BKPF, VBKPF            |
    |FCRD_VBSEG               |Include for Appends for VBSE*                               |
    |FDM_AR_CASE_ATTR_1       |FSCM DM:                                                    |
    |FDM_AR_LINE_ITEM         |FSCM: DM                                                    |
    |FDM_AR_RFPOS             |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
    |FELD                     |Screen Painter fields (internal)                            |
    |FICCO                    |Adjustment Values for External Document Items               |
    |FICCT                    |Totals Information for Interclient Posting                  |
    |FICTX                    |Tax Information for ICT                                     |
    |FIELDINFO                |Field attributes for a specific field                       |
    |FIN1_PARAM               |OBNG: Trans. structure for official doc. numbering (global) |
    |FIN1_PARAM_FI            |OBNG: FI parameters                                         |
    |FIN1_PARAM_MM            |OBNG: MM Parameters                                         |
    |FIPEX_STRUC              |Subfields Commitment Item                                   |
    |FIPOEXT                  |Help structure for line items to be generated automatically |
    |FIREVDOC                 |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS     |
    |FISTL_STRUC              |Substructure Fund Center                                    |
    |FM01                     |Financial Management Areas                                  |
    |FMBLSTRING_COMPONENTS    |Component of the BL String                                  |
    |FMCI                     |Commitment items master data                                |
    |FMDY                     |FIFM: Screen Fields                                         |
    |FMFCTR                   |Funds Center Master Record                                  |
    |FMFG_ACCIT_EXTENSION     |Extention for all fields that have to be transfered into BL |
    |FMFINCODE                |FIFM: Financing code                                        |
    |FMFPO                    |FIFM: Commitment Item                                       |
    |FMHRBA_NEG_DOC_TYPES     |HR Integration: Doc. Types for Negative Funds Commitments   |
    |FMHRBA_SETTINGS          |Integration with HR: Settings                               |
    |FMHRBA_VAD_SETTINGS      |HR Integration: Generate Value Adjustment Docs for Changes  |
    |FMICCN                   |FM: Append Structure for FMIOI (CCN Fields)                 |
    |FMIDATA                  |Common Data for Funds Management Actual Data                |
    |FMIDATAFI                |Clean FI Data for Funds Management Actual Data              |
    |FMIDATAOI                |Clean Open Item Data for Funds Management Actual Data       |
    |FMIFIIT                  |FI Line Item Table in Funds Management                      |
    |FMIKEY                   |Common Key for Funds Management Actual Data                 |
    |FMIKEYFI                 |FI - Key for Funds Management Actual Data                   |
    |FMIKEYOI                 |Common Key for Funds Management Actual Data                 |
    |FMIOI                    |Commitment Documents Funds Management                       |
    |FMIOIKEY                 |Key for Table FMIOI                                         |
    |FMIOI_USFG               | SD order needs quantity                                    |
    |FMIREF                   |Ref. Funds Management Actual Data to Preceding Document     |
    |FMISPS                   |General Parameters for Funds Management                     |
    |FMIT                     |Totals Table for Funds Management                           |
    |FMMRESERV                |Include for the Reduction of Funds Reservations (FM)        |
    |FMRFC                    |Function Modules and their RFC Destinations                 |
    |FMSP_SPLIT_FIELDS        |PSM Fields used in multiple account splitting               |
    |FMT001                   |Additional Customizing for Funds Management                 |
    |FMUP00T                  |Update Profiles                                             |
    |FMUP01                   |Update Control with Value Type Dependency                   |
    |FMUP_INV_KEY             |Extension for FM Update: FI Key of Invoice                  |
    |FMUP_PAY_KEY             |Extension for FM Update: FI Key of Payment                  |
    |FS006                    |Fields for Optical Archiving                                |
    |FTCHECK                  |Foreign Trade: Import Simulation - Ctrl Fields for Pricing  |
    |FTEXTS                   |Communication Structure for Additional Components           |
    |FTGENERAL                |Foreign Trade: General Fields Item                          |
    |FUND_STRUC               |Substructure Fonds                                          |
    |FVD_TZB0A                |Append to TZBOA: Loans Fields                               |
    |GLACCOUNT_CCODE          |G/L Account Master Record: Company Code                     |
    |GLACCOUNT_CCODE_DATA     |G/L Account Master Record: Company Code - Data              |
    |GLACCOUNT_CCODE_INFO     |G/L Account Master Record: Company Code - Information       |
    |GLACCOUNT_CCODE_KEY      |G/L Account Master Record: Company Code - Key               |
    |GLX_ORG_INFO             |Organizational Assignment                                   |
    |GMBSEGZ                  |Grants Management Add-on                                    |
    |GXXLT_H                  |XXL interface: horizontal features                          |
    |GXXLT_O                  |XXL_interface: texts for online display                     |
    |GXXLT_S                  |XXL interface: structure of the semantics table             |
    |GXXLT_V                  |XXL interface: vertical features                            |
    |HELPVAL                  |Restrict Value Range - Transfer Table                       |
    |HELP_INFO                |Transfer Values for the Help Processor                      |
    |HELP_VALUE               |Structure or Function Module HELP_VALUE_GET_FOR_TABLE       |
    |HHM_COBL                 |Include for COBL from FM                                    |
    |IADDR_PSO                |Local Authority Additional Fields (Address)                 |
    |IBKPF_PSO                |IS-PS: Include Structure BKPF Payment Request Doc.Header    |
    |ICDIND                   |Structures for generating change document update programs   |
    |ICON                     |Icons table                                                 |
    |ICONS                    |Icons                                                       |
    |ICURR                    |Interface for Currency Translation                  

  • Help required on OutBound IDoc for FI Invoices

    Hi All,
    I had a requirement to create a custom idoc for FI invoices via a user exit and these idocs will be routed (via RFC) to a JAVA server/processor. Pls suggest how can i acheive this.
    Is there any user exit for acheiveing this or can we proceed further without user exit also.
    If so how to acheive this.
    Thanks & Regards,
    Anil.

    One option that immediately pops up is
    Using Output Types: like for example transaction V/40
    Application: V3 Billing
    You can define a unique output type : ZINV
    Transmission Medium : 6
    Processing Routine
    Program:         RSNASTED
    Form Routine:    EDI_PROCESSING
    You can then use WE20, and define a unique customer / and map message control (ZINV) information in outbound parameters.

  • How to extract non-sap data (A/R Invoices from Legacy system) into SAP ICR

    Hi
    We are trying to bring A/R invoices from a legacy system into SAP ICR special ledger so that ICR tool can be used these items for intercompany reconcilliation. Could you please let's know the way to load these legacy AR invoice items into ICR data base using any function moduels.
    Regards,
    Eswar.

    Hello Eswar,
    In what form do you have these "external" open items? If they are contained in a file you should simply import the file in ICR during data selection using the File Upload functionality. There is no need to store them in a special purpose ledger first. Actually you would have to create a BADI implementation to extract the data from that special purpose ledger during data selection. Please consider using File Upload standard functionality.
    If for some reason this cannot be used you could implement a logic calling RFC enabled function module FB_ICRC_ADD_DATA_RFC which will take the open items you are supplying in your logic and push them into the ICR database. This strategy could be used to include these external open items without them being processed during data selection.
    Best regards,
    Ralph

  • Program making a RFC call to Function Module not working in background

    Hi All,
    I have an ABAP Program which is used to do a reconciliation check between the R/3 and BI system for Invoice Data. Please find below the details of the program flow:
    1.     Program counts the number of records in the DSO table and aggregates the Net_Value based on the date range (passed as parameters)
    2.     Program calls a Function Module (RFC Call) which counts the number of records in the R/3 table and aggregates the Net_Value for the same date range
    3.     Function Module Passes back the count values and aggregated Net_Value to the program
    4.     Program compares the count and aggregated Net_Value from EDWH and MSP systems and sends an email mentioning whether the counts match or not
    However we are facing an issue.
    Whenever, we execute the program in dialog mode, it works fine and fetches results within 5-6 minutes. However if we schedule the program to run in background (parameters through a variant), it gives no results even after running for over 3-4 hours. We tried figuring it out yesterday but could not come to any conclusion. Since there is a RFC call being to the function module, we were wondering if we need to specify some other parameter as well.
    Thanks & Regards
    Dharmendra

    RFC Call is a procedure for executing remote enables function modules. It is done via the 'Remote Enabled' radio button on the function module's attribute screen.

  • Argentina electronic Invoices

    I am currently working on Argentina's Electronic Invoices implementation and applied the OSS notes described below in my develpment system.
    I have some doubts about the SAP solution, as follows:
    - Is there any other OSS note that should have been applied besides the ones I have already done?
    - Does the solution cover Export Sales operation ? If not, is it any estimate from SAP to cover also export sales ?
    - Is it possible to implement the solution only for part of the operation , I mean, if I want to implement only for export sales for example ? I am asking that, because based on the solution proposed by SAP  the only way to do that would be by creating new document types, that would cause a huge impact in our environment. I think there should be a more reasonable solution for that.
    - Do you know if there is any SAP customer using the solution in a production environment ?
    - The SAP solution does not cover the communication with AFIP via Webmethods. Is there any plan to provide it ? I am not talking about the webmethods part, but the SAP part, like RFC, data base tables, SAP monitor, etc.
    After implementing the OSS notes we got some abap dumps, and for oine of them SAP said the would deliver the solution only in the next support pack, that is why I am not sure if the solution really works.
    I would appreciate if someone could give me a contact in SAP (phone number) who I could talk about the solution.
    Oss notes applied:
    OSS Note     Description
    858287     AR: Short dump during new official number group generation
    1131831     Note Assistant: Activating objects after termination
    1256910     Electronic Invoice for Argentina
    1273338     Argentina Electronic Invoice - Part 2
    1290612     Invoice picking SD documents belonging to different Company
    1291286     Rejection Description not displayed in Annexure 4
    1294647     SD Taxes and amount not translated to local currency in AEI
    1296640     In AEI SD documents,Sold to party is picked instead of Payer
    1298610     Branch determined incorrectly before creating Annexure 3
    1302949     Exchange rate determination Error while displaying AEI
    1305340     Downpayment not getting reduced from Final Invoice in ANNX3
    1312240     Enqueue lock error in J_1A_CAE & selection screen not shown
    1316834     In Arg Elec Inv, ODN not generated on Billing date in Annx3
    1321506     AEI - Incorrect Exchange Rate considered for SD documents
    1323731     Report J_1A_CAE for Annexure 3 enabled to run in background
    1324250     In AEI Annx 3 output file not sorted based on document date
    1327699     Performance Issue in Annexure 3 for Argentina EI
    1375796     Electronic Invoice for a foreign customer not considered
    1380007     Branch changed at the time of Elec Invoice Annx3 creation
    1391401     Amount not displayed correctly for Net Amount in Annexure 3
    1403671     Taxable base is displayed as negative value in Billing-Annx3
    1413253     Electronic Duplicate Invoice Functionality for Argentina
    1421109     AEI: Sales organization not accepted when running annexure3
    Thanks in advance for any response on that.
    Ulisses.
    5511 5088-5152

    Hi Ulisses Martine,Shankar,Carlos Daniel,Renan correa,Rudolf  and Victor,
    I need you guys help.The below is my clients requirement for number ranges for Invoices in SAP ECC 6:
    They have different Points of sales (POS) and they want different invoice number ranges from different point of sales.
    As you know SAP is having the Issuing branch concept and I have done below basic configuration for this but not able to get the number range for different issuing branch.
    Define Issuing branches
    Define document class
    Assign document class to document type (RV) >>later I have assigned this RV to billing type F2 (here my question is i have different document class for Invoice,credit memo ,debit memo etc. and for Invoice and debit memo the document type is same RV,how iI'll assign one or more document class to document type RV though SAP has provided it as one-one relationship)
    Maintain Number groups
    Assigned Sales area to issuing branch(here my question is if the i have more that one issuing branch for one sales area then how i'll go further)
    After the above configuration also I am not getting the different number range for invoice from different issuing branch.
    Please let me know if any one is having any suggestion for this or user exit or SAP note i need to follow.
    If you have any document please sent to [email protected], it would really help me.
    Thanks in advance.
    Regards
    Amar

  • Purchase Order history is not updated with Invoice number

    Hello Experts ,
    Please suggest some inputs/solution for my problem.
    Scenarios is :
    PO --> SO --> Invoice
    I am creating the invoice with the medium EDI , when I click on Save button IDOC is generated with the message " IDoc 'xxxxxxxxxxxxx' was created and forwarded for transmission " and it showing the status as 03 i.e, The IDoc was sent to an R/3 System or an external program via a transactional RFC ...but the problem is if I got to the Purchase Order history Its not updated with the Invoice number.
    What could be the problem , please suggest.

    Hi!
    I'm not sure, in which process you link PO and SO. There are some different ways, which are totally different scenarios - if you need help here, describe more detailed.
    Your invoice is probably only created with reference to SO, so check the invoice itself. In this case also the SO history should include the invoice.
    Regards,
    Christian

  • Batch job creation for sending email if the invoice is aged

    Positive confirmation: Send system notification to the requestor if:
    a) An invoice is received and GR is not yet posted in the ECC system.
    b) An 'aged' invoice and GR is not yet posted in the ECC system.
    This requirement is for USA only. i.e., we have only one company code which is 8960.
    Identifiers of the invoice are
    Company Code = u20188960u2019
    Invoice Document Type = u2018R9u2019
    Use table EKBE for relationship between Invoice, Goods Receipt and Purchase Order.
    The field EKPO-BEDNR contains the Shopping Cart Number
    Implementation Strategy
    1. To send email if the invoice is aged.
    Create a program that will run as a job. This job will frequently check for invoices related to SRM Shopping Carts received from E2OPEN. If an invoice is aged and there is no Goods Receipt posted through confirmation from SRM, then an email will go out from ECC system to the requestor. Using the Shopping Cart number on PO, find the requestor information (email ID) from SRM through an RFC call. This job will run once in a day and should have a parameter in the program for the age of the Invoice.
    Both the emails should contain a link (To be taken from SRM system, to be supplied) to log into SRM system. The email will also contain the Shopping Cart number and the Description of the item, and a message to Confirm this, including age of the invoice if aged.
    Please let me know how to create the batch job.
    Regards,
    Venkat
    Edited by: VenkatG on Sep 1, 2009 3:14 PM

    Do not pass the COMMIT_WORK flag... Leave it blank. Any transaction for the data integrity, one should never use COMMIT WORK related statements. Normally SAP transactions will have the COMMIT WORK at the end of transaction which is enough for any thing that is added part of the customer exits...
    Hope this helps.
    Regards
    Anjaiah

  • Create a Credit Memo from purchase invoice

    Hi everyone,
    I am trying to create a credit memo from a purchase invoice, but it retuns the following error:
    "RFC is missing"
    I am using the JCO classes to develop this application. this is a sample of my code:
    IDocuments document = SBOCOMUtil.newDocuments(company,new Integer(19));
    document.setCardCode("P00055");
    document.setDocDate(new java.util.Date());
    document.getLines().setBaseEntry(new Integer(2852));
    document.getLines().setBaseLine(new Integer(0));
    document.getLines().setBaseType(new Integer(18));
    int lRetCode = document.add();
    if(lRetCode != 0){
        System.out.println(company.getLastError().getErrorMessage() );
    Do you have any idea about what is the problem?
    Many Thanks.

    Hi everyone,
    the problem was solve. I had to specified the FederalTaxID field on the document.
    just added the following field:
    document.setFederalTaxID("000000000000");
    Thanks.

  • RFC destination error in posting 3rd party payment in 4.7 FI system

    Hi,
    We are running in to a problem when we are processing a payment via transaction F110S in our R/3 4.7 system for Financials. We are integrating our Financial system with ECC6.0 for HCM. We receive 3rd party invoice from HCM successfully via ALE and post it in 4.7 system. When we try to process payment against this invoice, apparently 4.7 system is trying to communicate with ECC 6.0 system and issuing an error and the payment processing gets cancelled. It generates a clearing document with out a check.
    The error says "An RFC destination could not be specified for the logical system HD1CLNT014
        Message no. B1550
    Diagnosis
        An RFC destination should be specified for the logical system
        HD1CLNT014. This could not be done in this case. HD1CLNT014 is not your
        local logical system and this system is not included in the relevant
        Customizing tables.
    Procedure
        Check:
            -   RFC destination
               -Port definition
             -oubound partner profile of message type SYNCH for this logical system
    We checked our configuration for all Logical system and RFC destination and everything seems fine.
    Any help in this regard is appreciated.
    Thanks
    Kesav

    Hi David,
    Did you check below is set-up correctly.
    - Use transaction SM59 to create an RFC destinations for the remote system.
    - Use transaction BD54 to create the logical system.
    - Use transaction BD97 to link the RFC destination created in SM59 with the logical system created in BD54.
    Also, check entries in TBLSYSDEST is  filled with correct system name HPQCLNT210. Generally this error occurs when system name is incorrect in TBLSYSDEST.
    Thanks,
    Ameet

  • Invoice image in vendor and customer document

    Hello,
    We have got following requirement.
    Currently we are storing pysical invoice copies of vendor and customer in a pysical file. But now we want to see the image of invoices in vendor and customer document respectively.
    It means, if it is possible to have an attachment button or some icon available when we see vendor and customer document.
    Please advise how can we link the pysical invoice with SAP document. And is this something related to DMS or Archivieng Link.
    Please suggest.
    Best Regards,
    Tapan

    Hi Tapan,
    At my company we are currently doing just this.
    We have a server outside of SAP that stores our images.  We did not want to store the images within SAP.
    We use the SAP document number to link the image to the SAP document.
    We do all our AP input from images. After an invoice is entered, and the document number is generated, we forward the image to a
    e mail address for the server using the document number in the subject line. The image gets attached to the document. Then the image can be viewed by clicking on the Services for object icon.
    I am sure there is some more techical stuff that goes this, like an RFC connection. I am sorry I am not technical. I am the functionala AP person. We also have a program that takes the image and attaches it to the cross company document if there is one.
    Hope this gives you some ideas.
    Alicia

Maybe you are looking for