Interface for AR INVOICE attachment
Hi,
i insert to RA_INTERFACE_LINES_ALL interface for doing conversion for my AR invoice. But recently my customer wants to use the attachment on AR INVOICE and AR INVOICE LINE for storing some information.
What is the interface table name that i can use? i notice the base table is fnd_documents_short_text. What is the SQL statement to show the result given the AR INVOICE TRX NUMBER?
using 12.1.3
the attachment type is short text.
any interface table available?
Similar Messages
-
Standard interfaces for vendor invoice and salary posting
Hi all,
Our customer is asking for a standard interface for vendor invoices (not purchase invoices, only for invoices entered in FB60), if they could have a CSV file from vendor and import that to SAP. Is there a standard functionality or do we have to build an own interface?
They also ask if there is a standard interface for salary file so they can tell the company that create the salary file that they should use a standard format or do we need o to create an interface there to?
Thanks in advance!
BR LHi,
You can either go with INVOICE01 or INVOICE02, As per the requirement you can check with the Function module attach with the idoc type, and whether it is providing the appropriate functionallity or not.
Thanks & Regards,
Navneet Chaubey -
Accounting Document not posted for Cancelled Invoice -error in FI interface
Hi,
When I create a billing document then an accounting document gets created automatically in the background and then when I cancel the billing document no accounting document gets generated and the field Posting Status in header Detail of Billing document updated as "Errors in Financials Interface.
I tried to release it for Posting via VFX3 but failed due to below error message in Log:
"Incorrect doc.no.: 4900000005. Select document number between 3000000000 and 3099999999"
I have checked the Number range assignments to the Invoice type and Accounting type.
The number range is same for both Invoice type (Y0F2) and Cancelled Invoice type (Y0S1).
The Accounting document type (RV) is also same for both the cases. But it is working fine for Y0F2 (Acounting document generated and cleared automatically). But not working fine for Cancelled Invoice (Y0S1).
Can anybody please help me find out a solution to the issue.
Thanks, Ram.Hi,
The error message F5151 refers to the number range of the FI document.
Please have a look at the note 1259505: FAQ: New cancellation procedure in SD, which covers this issue in detail.
Question 5:
Q5. What is the FI document type, generated by the cancellation ?
In the old cancellation procedure, the FI document type is always
determined in SD, and passed to FI (the same when a normal invoice -
not a cancellation - is transferred to accounting).
In transaction VOFA there is the field 'Document type' (TVFK-BLART).
If this field is filled, then the FI document will have the document
type maintained here.
If TVFK-BLART is empty, then the FI document will get the default
document type 'RV'.
If the new cancellation procedure is performed, the FI document type is
always determined in FI, based on the document type of the FI document
to be reversed.
In transaction OBA7 the FI document type has assigned the field 'Reverse
document type' (T003-STBLA).
If it is filled, then the FI cancellation document will get the document
type maintained here.
If T003-STBLA is empty, then the FI document cancellation will get the
same document type as the cancelled FI document.
Notice that an unexpected FI document type can cause the error message
F5 151.
Example:
F2 invoice 90000001 was released, creating an accounting document with
document type 'RV'.
This F2 invoice is reversed by the S1 billing document 70000001.
In customizing of SD there is:
Billing Type Document Type
F2 RV
S1
In customizing of FI there is:
Document Type Number range Reverse Document Type
RV 00 AB
AB 01 AB
The FI number ranges (object RF_BELEG) are:
No From number To number Ext
00 0090000000 0099999999 X
01 0100000000 0199999999
Different situations can occur, due to these customizing settings of the
FI document type, caused by the type of cancellation.
If the new cancellation is used:
The FI document type 'RV' has 'Reverse Document Type' = 'AB'.
Document type 'AB' has number range '01' set as internal.
So the FI document will have its own number included in
100000000-199999999.
There is no issue.
If the old cancellation is used:
The cancellation billing type S1 has no 'Document type' maintained, so
the FI document will get document type 'RV'. It has number range '00',
set as external number range.
So the FI document should get the same number of S1 billing document.
But the S1 billing document has number 70000001, not included in the
interval of number range '01'.
This will cause error F5 151.
I hope this information helps you. -
Disable 'Delete' button for posted invoices in GOS Attachment List
Hi,
when i open the attachement list of a generic object i see the attached files. In this dialog i want to disable the "Delete" ( attachment) button for Posted invoices ( In MIR4 tcode -> If the invoice is already posted it should not allow to delete the attachment )
I read oss notes and some ides of copying diverse classes but nothing really helps.
I found two badis
GOS_SRV_REQUEST
GOS_SRV_SELECT
but i dont know where we have to write our code .
I read so many posts related to attachments but all the places described about authoriztion object .
Can you please give some ideas to disable the delete button for posted invoices.Hello,
For GOS there is no SAP Standard authorization concept. The only way to
manage GOS authorizations is implementing it via custom code as
described in SAP Note: 491271.
Please have a look at the SAP notes:
491271 Authorizations for generic object services
701609 Authorizations for services: Final classes
For the use of S_OC_ROLE: this object states if a user is an office
administrator he can create, modify or delete every document, even
those created by other users. If the user is not an office admin, the
user is still able to create his own attachments.
Regarding to the issue, there is an role object S_GUI for upload.
To match your inquiry, pleaes find the user's role and active the
object S_GUI.
Regards,
David -
PDF Form interfaces for invoice
Hi experts,
I`m implementing company forms (e.g. invoices) in PDF Forms. But I have found, that there are 2 form interfaces predefined for invoices
IS_U_BILL_IF
and
IS_U_BILL_PDF2_IF
Why there are 2 interfaces for invoice? I cannot find any references of use cases, when to use first or second one.
Thank you
VladoAs noted there has to be a special folder level script installed on each user's system. This script can be written to access individual properties of the identity object or only a specific property. One can also create a function to access the identity object or even create new properties.
-
Object type for Vendor Invoice (FB60) to attach image
Hi,
I was wondering if any of you experts would know the Object Type for Vendor Invoice which allows an image to be attached to it in early archiving.
Many thanks
GThe object for attaching an image to a document entered directly into FI is BKPF. This is the object for vendor invoices entered into FB60 as well as vendor credit memos (FB65), customer invoices (FB70), customer credit memos (FB75) and GL adjustments (FB50). It also applies to any document posted via a complex (non-enjoy) FI transaction like FB01.
-
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.
-
Interface of Excise invoice procedure
For the system to follow my excise invoice pricing procedure, how to interface it with my main pricing procedure?
adding excise tax as a tax in my pricing procedure does not permit me the concessions to be used on presenting the C form.
plz guide me for the tax and pricing procedure interface.hi,
thanks for putting some light on the matter, still am not very clear as how it should be done.
one of the method is that i add a customized cond type-excise tax of 16%(e.g. zexc) in one of the sales doc type
create another sales doc type which offers exemption of excise tax on presentation of C form, or create another sales doc type which has no tax liable to it.
second method is that i create a sales order, create proforma invoice for sales order and maintain a copy control of excise invoice from the proforma invoice for order and attach the tax procedure (e.g. JFACT, JDEPT, JEXPO to the billing type ZJX - Excise invoice type)
or else if there is anyother option plz help me out in it.
thanks. -
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 -
Early Archivelink for vendor invoices
Dear All,
I want to use Early Archivelink for vendor invoices scenario.
I am attaching the scanned document through OAWD by Storing by subsequent entry and i am able to see the work flow item in my in box but i am not able to execute the transaction from here(MIR7).I am using business object BUS2081,method create and task TS30001128.
Please advice how to execute the work flow item from my in box and create the invoice document.
Regards,
MuzamilHi,
After maintaining the TS 30001128 as a general task i am able to execute the transaction from my inbox.
Regards,
Muzamil -
Business object type for parked invoices
Hi,
We are using documentum to store documents that have been attached to business object types in SAP. The business object types are configured in transaction OAC3 to point to a pre-configured content repository.
Having this configuration allows the object type to use the "services for objects" option, enabling it to store attachments.
The business object types for invoices have been configured and we are able to store attachments. However this does not seem to work for "Parked invoices". The configuration in the "services for objects" component is not there and the feature to store the attachment is disabled.
As the configuration needs to be done for all object types that need to be able to store attachments, maybe someone here can indicate what the object type is for parked invoices. Alternatively, maybe there is a way to look up the various business object types.
Any help you can provide is appreciated.
Thanks.
Kind Regards,
GiwanHi ,
Thank You for your reply.
I created inquiry . it takes BUS2031.But BUS2031 is used for quotation.But that inquiry is open in VA12(Change Inquiry) Transaction,not open in VA22(Change Quotation).
Is there any setting for BOR object types to Document Types.
Please give me a reply as early as possible.It's very urgent.
Thanks,
Saritha -
Excise Invoice Print problem for multiple Invoices
HI All,
I Have developed a Zprint prog and zsmartform and attached it to standard tcode J1IP .
when we execute J1IP outputtype J1I10 we get multiple invoices . if we select one check box and execute and press print preview/ print we get the print correctly . But if we check multiple check boxes and press print/preview then we have to press print button multiple times/come back for every invoice .
My requirement is when we execute J1iP for multiple invoices it should not come multiple times pop up window ..ie in one print request we need to send multiple invoices . How to achieve this functionality.Hi,
use NO_OPEN and NO_CLOSE fields of CONTROL_PARAMETERS structure
in Your call to smart form function module.
Currently You print every invoice in separate spool request.
You should print all invoices in one big spool requests.
Set NO_CLOSE = X to all, except last one, and NO_OPEN = X to all, except first one.
Regards,
Przemysław -
Excise invoice Print for multiple invoices
Hi All ,
i have developed a z smartform and attached to standard tcode J1IP o/p type J1I0 . The o/p is comming fine when i select one excise no after excecuting tcode J1IP But if selected multiple invoices by checking the checkbox and press print preview or print
button each time it is giving print preview/print diaog. i.e i need to execute print for first invoice and again i have to come back and again it will ask print prview/print dialog for second like wise n times for n no of selected documents .
my requirement is like when i execute tcode J1Ip and when i select multiple invoice i should get only one print preview or print dialog for all documents . how to achieve thisHI friend,
Its simple.
Put all the invoices in a single loop. I think you will be calling the smartform function module for each and every invoice. Don't do like that. Just collect all the invoices in the final table first and after that display the invoices.
I think you can understand what i am saying.
Please try and let me know if you have any queries i will help you.
Thanks,
Sri Hari -
A more successful experiment in creating compositable user interfaces for Config Dialogs
A couple weeks ago I posted an experiment in creating compositable user interfaces using transparent subpanels. The approach might best be described as, "It at least was notable for being novel."
Today, I'm posting another attempt, this one along more traditional lines, and far more successful. Particularly notable: this one can do all the arbitrary composition of the last one AND it solves the TAB order problem.
This solution uses a picture control and renders N copies of a control. When the user tabs to a control or moves the mouse over the control, a real control slides into that position to be able to catch the events (update mouse over draw state, highlight for keyboard focus, handle typing, etc). When the Value Change occurs, a master array of data is updated and the picture control is updated.
This is something that has been attempted in various forms in the past, but there are two aspects of this particular implementation that make it nice:
its programmatic interface for specifying the behavior of the various objects should make it fairly easy for a user of the framework to programmatically generate their dialogs
it handles the TAB problem without flickering, something I haven't seen in other attemps
This idea spawns out of conversation about the previous experiment -- thanks to those of you who posted on various forums, e-mailed me, or, in a couple cases, showed up at my desk. That last one is not something I'm encouraging unless you work at NI... just saying. :-)
Now, this experiement has already yeilded some interesting conversation. We note that as long as controls are instantiated independent of each other -- that is, no property of one control depends upon the property of another control -- this dialog system scales nicely. But in this experiment, I implemented Radio Buttons, which interact with each other -- when one is set True, the others go False. As soon as controls start interacting with each other (such as graying out one control when a checkbox is toggled, or having expandable sections, or really complex cases like updating a graph as some options change, like happens in some Express VI config dialogs) then we start needing ways to refer to the other controls. This rapidly moves us in one of two directions: naming controls or creating references. The naming approach is definitely my preference as it fits better with dataflow and I can do some interesting effects with breaking apart some of the tree. But all of this quickly starts sounding like "Please implement a XAML parser in LabVIEW." For those of you unfamiliar with XAML, in the world of UI design, it might very well be the coolest thing since sliced bread. A XAML string would indeed fit with dataflow, and we could start building that up. I hesitate to head down this road for two reasons. One, as many have noted, there's really not a good XML parsing library written in LabVIEW that can give me a useful DOM tree. Two, that's a huge project and my gut sense is that you'd have to complete a fairly large chunk of it before you'd start seeing any return on investment. But it is worth thinking about -- I might be wrong. Wouldn't be the first time. This code that I've posted today can at least get you started on the generation side if one of you decides to become industrious.
I'm turning my attention away from this project for now... coding in G is lots of fun, and I wish I could spend more days doing it, but this has been a side project and it's time to get back to my assigned projects in text programming. Building a powerful platform for automatic UI generation in LabVIEW would be really useful -- I see lots of requests for this sort of thing, and other languages are pulling ahead of us in this domain.
[UPDATE 5/17/2012 - There is an improved version.]
Solved!
Go to Solution.
Attachments:
ConfighThroughCtrlCreation.zip 558 KBElijah K wrote:
Thanks for posting this Aristos. I would normally be one of those to go bug you at your desk, but in case I'm not the only one with this question... which particular flickering problem are you referring to? The act of switching tabs? In all honesty, I've never noticed...
When you move controls around on the screen, normally you try to Defer Panel Updates while you do that. But Defer Panel Updates has an effect on control's abilities to catch certain mouse clicks, so when you're trying to move a control to catch the mouse, you have to work a lot without Defer Panel Updates, so if you're adjusting captions, etc, to match the new location, you can see flicker as properties adjust. You can move the control off-screen, as long as you have already updated the picture control to reflect the changes. It took a while to catch all the ways that the flickering can crop up. I think I got 'em all.
Attached are the VIs saved for LV 2009. Actually, they're saved for LV 8.6, but it doesn't work in 8.6 because of a bug in the picture control that existed back then.
Attachments:
ComposableUI_LV2009.zip 391 KB -
SD - Two message category for an invoice document type
Good morning all,
I use InterCompany biling in SD with standard invoice document type 'IV' and message category 'RD04' (which enables vendor invoice creation).
My customer asks to be able to print a form for the intercompany bills.
For the non intercompany bills this is actually performed by using a specific message category.
So my question is : is there any way to have TWO message category ('RD04' + specific message for form) automatically attached to an intercompany bill (customizing, user-exit,...) ?
Best regards.
Didier GOBLET.Hi Didier
Assign the logic to the RD04 output type smartform.Then it is possible,In the smartform include the logic that it should automatically attach to the intercompany billing.
Regards
Srinath
Maybe you are looking for
-
Hi Guru's I would like to ask some questions on ABAP query. 1. Can you transport abab queries? Should it only be Global or you can also transport Standard Areas? 2. Once transported, am i able to change query? Thanks, Jograd
-
Activating u00E1 former Window after calling a Document management picture
Hi, in an ABAP programm I am calling function module CVAPI_DOC_VIEW2 which opens a new window where I can view a Document management picture for a given material number. My problem is, that the new called window is active and I have to use a mouse cl
-
What is a best way to write SQL ?
Sample Case drop table t; drop table b; create table t ( a varchar2(4), b number, c varchar2(1)); insert into t values ('A00', 10, 'R'); insert into t values ('A01', 11, 'R'); insert into t values ('A02', 12, 'R'); insert into t values ('A03', 13, 'R
-
The 10.6.4 and iTunes update disabled viewing cover art in mp3 file icons. Anyone have a solution?
-
Cannot open any Internet Explorer files
Here's the other question. ( I have Tiger. I still have OS 9 with Classic. ) 2) when I click on a file in Mac Intosh HD that was created under OS 9, with Internet Explorer 5.1.6, a file with the IE logo (the letter e + a globe), I see now a message s