EDI for Consolidated Invoice
Hi All,
We have a requirement to send EDI to customer who are on Consolidated Invoice. I have used standard SAP Idoc Type INVOIC02 with message type INVOIC. I used the Output type RD01 and then created a Consolidated Invoice. The problem is the segments that are populated for this IDOC type doesn't have the reference Invoices. Does anyone of you have an idea on what is the standard IDOC type that i can use for EDI for Consolidated Invoice. I will appreciate if someone can help me in this. I treid reading various threads and the experts here are mentioning about EDI 811.
Can anyone of you help me in this regard.
Thanks
Ashit Taneja
Hi,
Can you throw some more light on what is the IDOC type that i need to use for that. I can understand you are saying that 811 is for Consolidated Invoice, but i need some more clarity on the IDOC type, the message type and the segments which are populated. I tried using the IDOC type INVOIC, but the segments that are populated has only the Consolidated Invoice number and doesn't have the referenced Invoices.
Similar Messages
-
EDI for Services Invoices from CRM
Hi All
Does anyone know if it is possible to output billing documents from CRM to external customers via EDI?
Cheers
GavinHi Gavin,
I havent sent invoices via Idocs from CRM but have done so for Service orders. You have to find the correct replication object to use, one that allows you send Bdocs through the External Interface (XIF adapter) that will convert the Bdocs into xml/Idocs, for example the object BEABILLDOCFINA looks like it will send bodcs from CRM to the XIF. In smoeac you have to set up a new site with XIF as the site attribute which lets you specify an EDI partner profile for IDocs or an RFC destination for XML, then assign a subscription that references the Bdoc replication object BEABILLDOCFINA . Then when you have done this maintain an entry CRMXIF_C1 which links the site and Bdoc to an XIF interface, there seem to be a number of interfaces for invoices CRMXIF_INV_RELE_SAVE. This interface is where the mapping from Bdoc to Idoc or XML file is done. If you are using Idocs then you need to ensure that you have the correct partner config set up with the IDoc type assigned. THe idoc types seem to be CRMXIF_INVOICE_SAVE_M01 or CRMXIF_INVOICE_SAVE_M02 .
Cheers
Paul -
Consolidated invoice needed for different shipment dated lines in a sales order
My client's requirement is, they need a consolidated invoice for one order even though the lines are shipped in different dates.
Suppose order A created with 2 diff line B and C.
Both the lines are having different line types, sales persons and shipping warehouse.
Line B shipped earlier and lince C shipped after few days.
Requirement is to generate single invoice for both the line once all the lines are shipped.
Could you please help with any solution except Invoice Hold and Fulfillment Set.Hi All ,
Thank you all for your quick respose . Let me give your more info for a better understanding of my requirement . Basically here two prices are to be compared . List price which is based on sales org / distribution channel and material . The other is special price matained for sales org , customer and material .
In my system I have 2 different pricing reports ( T- code SAP1 ) , one is based on sales org , material - This I can use to find list price . I also have another customer based report and using this I can get the special price
But user wants to see both these prices side by side in a single report . Is there a way these two reports can be combined ?
Regards
Raghav -
Seeburger help required for Supplier Invoice (EDI 810) and Dispatch Advice
Hi All,
Pls let me blog/steps for scenario for Supplier Invoice and Dispatch Advice using Seeburger.
For Supplier Invoice I assume R/3 will send data to Vendor (810).
1. Pls let me know for R/3 to XI will we use INVOCE IDOC?
2. Pls let me know for R/3 to XI Communication do we will use same Distributiion Model setup?
3. Pls let me know what Seeburger BIC modules I need to use in Seeburger AS2/File Receiver Adapter
4. Which Interface and Adapter I need to use for 810 and which Interface and Adapter I need to use for 997.
Pls send its setup with its Mappings defined in Modules.
5. What is Disptach Advice? Is it also same like Supplier Invoice ? Does it also have EDI Number and if yes then what?
Pls send me blogs for the above Supplier Invoice and Dispatch Advice settings.
Regards>
Rickkk wrote:
> Hi Ravi and All
>
> I am thankful to all of you for great help of yours.
>
> Steps:
>
> 1) I wil create an INvoice in your backend system. It will generate an IDOC.
> 2) This IDOC will be sent to my XI system.
> 3) I will map the IDOC to the Target XML 810 --- From where I will get this Target XML 810 ?
YOu have to login to the Physical box in which XI is installed (Take Basis Help.
In one of the drives, you will find a folder called seeburger.
Inside that folder, you can browse to find the XSD structure for your 810 .
YOu will find different XSDs for different versions of 810.
Suppose your EDI 810 version is 4010, then you have to use the XSD for 810 4010 version (There will be separate folders for each transaction set/version combination.
It will be there also in the software CD that seeburger provides when you buy it.
> 4) I need a seeburger receiver AS2 adapter that consist of modules that will convert the XML 810 docuemnt to EDI document.
>
> Below are the modules will be present in you suggested seeburger receiver AS2 adapter
> module key Parameter name Parameter value
> bic destSourceMsg MainDocument
> bic destTargetMsg MainDocument
> bic mappingName <the name of your X2E mapping for 810>
> exit JNDIName deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
>
Yes.
> 5. As per blog -
/people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
>
> For 997 Interface we are using seeburger Sender adapter and for 850 Interface we are using Split997 Sender adapter -- Reverse order
>
> For this scenario will it be like this again like
> For 997 Interface we will use Seeburger Receiver AS2 Adapter where the above modules are configured -- Pls suggest
>
> For 810 Interface we will use Split997 Receiver adapter -- No modules configured Pls suggest
>
> I request you to kindly send me snapshots or blogs which has snapsot for this scenario.
>
No need of split 997 in outbound case. In this case, you will send the 810 and the partner will send the 997.
So, to receive that 997 file, you need another scenario. You need the split 997 communication channel only in inbound case like in 850, but not in outbound case.
> Last point -- is Dispatch advice direction is like 850 (Inbound ) or its direction is like 810 (outbound)?
> Do we have IDOC or something like that present and its mapping ?
>
like I said earlier, it is an outbound document if your company is the vendor.
It will be inbound if your company is the Customer to some other company.
The IDOC that is used usually will be DESADV idoc.
> Regards -
Want to configure Oracle EDI Gateway for Inbound Invoice Interface
Hello,
Newbie to Oracle Apps and want to configure Oracle EDI Gateway for Inbound Invoice Interface. We are having Oracle EBS R12 installed on OEL 5.6
Do i need to install EDI Gateway or it comes with APPS R12 installation ? if i have to install it explicitly then which EDI version i have to install ? what are steps should i follow to achieve desired results.
One more query, we are having old version of Oracle APPS 6i too, is it possible to configure Oracle EDI Gateway on it ??
You help will be highly appreciated.Try to post your message on dedicated EBS forums http://forums.oracle.com/forums/category.jspa?categoryID=3.
-
SD EDI configuration for sending invoice to customers
Hi,
Could anybody please tell me what all SD configuration i need to do in
SPRO-->Electronic Data Interchange section for sending invoice through EDI?
I have already done output type configuration and able to generate IDOC when i save my invoice.
Thanks,
Regards,
SatyaHi All,
Thanks for the response.
But majorily i am looking for SPRO>Sales&Distribution>EDI configuration.
Do i need to do it?
Is it mandatory?
Thanks in Advance.
Regards,
Satya -
Invoice print supression for consolidated billing customers
Is there a way to tag a customer identified as eligible for consolidated billing to not print invoices other than consolidated bills.
I would like to identify by customer site rather than by transaction type.Hi,
I am not losing any details or neither losing a location of a particular text but my problem is in PRoduction when i randomly printpreview multiple page invoices for the first time the details are jumbled up,for instance certain fields are outputted correctly like PO number price etc,but certain fields like material,description,quantity are all jumbled up.Parallely when i open a print preview of the same invoice in other screen or i try to take a hard copy the details are all displayed properly.
This error does not occur subsequently and is very sporadic in nature.Any idea why this error could be occuring? I have also check with basis regarding different printers he has eliminated this.
Regards
Mohammed Roshan -
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 -
Accounting documents are not posted for Excise invoice
Hi,
1. The Excise invoice has been created with reference to F2 invoice but the accounting documents is not posted for excise invoice, what is the settings needs tobe maintained to post the accounting entries to excise invoice..?
2. where we will maintain number ranges for excise invoice..?
Thanks
Rao..hi
1. The Excise invoice has been created with reference to F2 invoice but the accounting documents is not posted for excise invoice, what is the settings needs tobe maintained to post the accounting entries to excise invoice..?
Not sure but can u try to relese this to accounting
2. where we will maintain number ranges for excise invoice..?
Excise invoice number range is depend on Excise series group.
T-Code : SNRO
Following is the No. Range Objects related to Excise, select the proper no. range object as per your requirement.
J_1I57FC - 57FC Number Range
J_1IARE1 - ARE1 Doc No object based on Series Group
J_1IARE3 - ARE3 Doc No object based on Series Group
J_1IBOND - Excise Bonding: Bond number object
J_1ICERT - Withholding Tax Certificates (India)
J_1ICHLNNO - Internal number range for challans
J_1ICONPLA - Consolidated PLA serial no. generation
J_1IDEPINV - Excise Invoice Number for Depot Invoices
J_1IEXCEXP - Export excise invoice number range
J_1IEXCINV - Excise invoice number
J_1IEXCLOC - Local excise invoice numebr range
J_1IEXCTST - Excise invoice with intervals
J_1IEXINEX - Excise invoice number for export
J_1IINTNUM - Internally document number to be generated
J_1IINTPR2 - Despatch serial number
J_1ILIC - Excise Bonding: License number object
J_1IPLA2 - PLA part II number range object
J_1IRG1 - RG1 Number range object
J_1IRG1_T - No. Range for RG1 - Excise group / Material
J_1IRG23A1 - RG23A part 1 no. range object
J_1IRG23A2 - RG23A part II number range object
J_1IRG23C1 - RG23C part I number range object
J_1IRG23C2 - RG23C part II number range object
J_1IRG23D - Folio Numbers for RG 23D
Check the link
Re: Excise Invoice Number Range
excise invoice and domestic invoice sharing same number range -
A report to see the consolidated invoices
Hi,
Are there any standard reports which would display the consolidated invoices for a customer who can carry out consolidated billing?
Appreciate your help.
Thank you.Hi,
List of standard report available related to billing/customer balance:-
VF05 - List Billing Documents .
VF25 - List of Invoice Lists
VF04 - Process Billing Due List
S_ALR_87012197 - List of Customer Line Items
S_ALR_87012178 - Customer Open Item Analysis by Balance of Overdue Items
S_ALR_87012168 - Due Date Analysis for Open Items
S_ALR_87012186 - Customer Sales
S_ALR_87012172 - Customer Balances in Local Currency
S_ALR_87012169 - Transaction Figures: Account Balance
S_ALR_87012171 - Transaction Figures: Sales
would this help?
regards
Vivek. -
Payments for Consolidated billing
how receipts are applied to the Consolidated billing number?
Thanks,
Prudhvi.
www.erpschools.comHi
Hope you know the set up for Consolidation Billing. If you enable the Show Billing Number check box in system options form in AR, then while creating Sales Invoices you will find the Transaction number field split into two. One for Consolidated Billing and the other field for Transaction Number.
When you create a Receipt and apply to an Invoice also, you will find the same two fields for Transaction number. You can choose the Consolidated billing number and the Transaction Number to whcih you want to apply the receipt
Hope this helps
Regards
Sivakumar -
TAX ASSESSMENT BASIS MISSING IN SEGMENT E1EDK04 FOR IDOC INVOIC
Hello,
Tax assesment basis is missing in segment E1EDK04 for IDOC INVOIC. In EDI messages,Tax assesment basis has to be sent in TAX segment together with VAT rate. When there is only one VAT rate this is not a problem as tax assessment basis is the total net amount (And we have it in the IDOC). On the other hand when there is more than one VAT rate in the invoice, we don't have in the IDOC the Tax assesment basis of each VAT rate.
Did someone experience this issue ? How did you handle it ?
Regards.
Eric.Dear Eric
The latest pack available now for these components are (for PI 7.1)
SAP BASIS 7.11 support package 6
SAP HR 6.04 with Support Package 44
If you are in PI 7.0 then I suggest you download the latest patch from marketplace.
Sourabh -
Any Idea Which Message type/Idoc Type should be used for FI Invoice
Hi Experts,
Any idea what message type/Idoc type should be used for FI invoice. We are going to send IDOC from R/3 to Non-SAP System using ALE. We are using T-codes FV60/FV65.
Thanks,
SonyHi Sony,
I never dealt with FI IDoc.
I think you need to setup EDI outgoing payment in IMG. Please take look this report <b>RFFOALE1</b> - ALE Distribution of Payment Data and <b>RFFOEDI1</b> and check also the program documentation.
Hope this will help.
Regards,
Ferry Lianto -
Purhcase Orders for Renting - Invoice plan
Hello,
I would like to know if anyone of you has had experience with the folowing business situation:
Renting of equipment or vehicules:
A company has a contract with a particular vendor for renting equipments and /or vehicules.
If a particular Plant needs to rent a vehicule for lets say 2 years, the purchasing department creates a Purchase Order with 2 years term on the basis of which, the supplier invoices monthly a pre-established amount.
To complicate a bit further, the monthly invoice from the vendor in a lot of cases is for the total amount of vehicule renting in all plants of the company.
Also we want to use Contract -management in SAP for the renting of vehicules in which the monthly invoice is consuming the amount agreed in the contract.
How can one map this business case in SAP without using the funcionality of an Invoicing Plan (our client does not want to generate the invoice automaticaly)
Note: We do not use the Goods/service Receipt funcionality of MM in this proyect.
I looked at partial invoicing but then the total amount due at a certain date is shown in the MIRO transaction and not the monthly amount due to be invoiced.
Can anyone help me. Give me some clues how I can resolve this Case in SAP.
Thanks,
AartHi,
The periodic invoicing plan is the best one which would suffice your need. But as you have mentioned that you dont want to have the automated invoice generation, you can go for Blanket / Framework orders (FO doc type). Here you would need to give the limit value and the validity period for the agreement with the vendor. you would not require the GR or Sevice entries to be done. You can create manual invoice verification- IR. The only drawback is that you cannot get the monthly fixed amounts defaulted in the Invoice verification, manully the monthly amount has to be entered- everytime you create the invoice.
Also the PO and invoice verification in MM will always be plant based. So if you want to do this processing in a consolidated way (if consolidated invoice will be received) then you can also look out for options in FI module. I hope Lease accounting can provide you some option here. check with your FI consultant.
Regards,
Kathir -
Hi All,
I have a smart form for standard invoice that is attached to the output type RD00, now the consolidated invoices are also to be printed thorugh the same form but with the consolidation based on ship to, sold to , Cust PO and ship date .
for standard invoice I am using VF02.
Can anybody suggest how to deal with the same smart form and what modifications are to be done for the consolidated invocies?
What may be transaction for the same?
Thanks & Regards,
Anuj SaraswatHi
Creating a smartform which caters both the needs is difficult. Because It needs huge layout changes.
I dont know if it would work but If u have time try creating two different layouts..and create an alternative flow logic to choose it based on the condition to create a standard smartform or consolidated one.
YOu should have clarity on the fields you want to display in the consolidated smartform..
Regards,
Vishwa.
Maybe you are looking for
-
How do i sync my notes from my mac to iCloud?
Hi there, I've been trying to sync my notes between my iphone, ipad and macbook. I'm able to sync them between my ipad, iphone and icloud, but I can't do it from my macbook. That's really what the whole point of this exercise is - there are a lot o
-
Connected to wifi but can't connect
I have been able to connect before but when I came home from college I can no longer connect. I am able to receive email and check the weather but cannot use safari. Help?
-
Oracle Rules: Adding Java Facts - not showing up in list.
I am having trouble with adding my own Java classes to the Java Facts. I find the class in the list of classes, tick it, and hit "Ok". When I come back to the list of Java Facts, the class has not been added to the list. And no error message is displ
-
Hi all, I have read what has been said o nthis topic on the boards. I have my Apple TV with an optical out and HDMI out both going to a receiver. I can switch receiver HDMI outputs (watch a show on tv) with the Apple TV sound still working. Howeve
-
Need of exception handler in calling function, isn't that weird???
Hi, I have written a function as follows public String fetchName(String query) throws Exception stmt = con.createStatement(); ResultSet rs = stmt.executeQuery(query); rs.next(); return (rs.getString(1)); I've h