Table for Intercompany GL Matching

Through closing process there is a step which generates transactions in the 1111 company to eliminate interco movements.
SAP is recognizing through this process which accounts match together. Example if an entry is made in company 0180 account 1470100 and SAP doesn't find in another company of the group (ie 0881) a similar entry in account 2230100 then it generates automatically an entry in company Z350.
There is surely a table in SAP which enable to see which accounts should match together.
I'm looking for the list of all accounts which offset each other through the elimination step.
I know already that : 1470100 is linked to 2230100, 1470200 to 2230200 ....but i don't have a complete list of all accounts.
thanks

Hi Praveen,
Please check table T001U.
Thank you.

Similar Messages

Table for 2way,3way matching .query to generate invoice with 2 ways matchin

hi
table for 2way,3way matching .query to generate invoice with 2 ways matching
plz help me
thanks

Hello John, I put the (1,2,3) list in the query to show it works with multiple invoices.
You should comment out the conditions:
select a.invoice_no, b.child, sum(a.amount) from invoice_detail a,
select
child,
decode (instr(scbp,'.'),0,scbp,
substr(scbp, 1, instr(scbp,'.') -1)
) starting_child
from (
select ltrim(sys_connect_by_path(child,'.'),'.') scbp,
child from
element_relation
start with child in (select element_id from invoice_detail /* where invoice_no in (1,2,3) */)
connect by child = prior parent
) b
where a.element_id = b.starting_child
/* and a.invoice_no in (1,2,3) */
group by a.invoice_no,b.child
order by 1,2to show it works for all invoices
regards, Tony

Updating values with in the same table for other records matching conditions

Hi Experts,
Sorry for not providing the table structure(this is simple structure)
I have a requirement where i need to update the columns of a table based on values of the same table with some empid and date match. If the date and empid match then i have take these values from other record and update the one which is not having office details. I need the update query
Before update my table values are as below
Sort_num     Emp_id   office      start_date
1                      101     AUS    01/01/2013
2                      101                01/01/2013
3                      101               15/01/2013
4                      103     USA    05/01/2013
5                      103               01/01/2013
6                      103                05/01/2013
7                      104     FRA    10/01/2013
8                      104               10/01/2013
9                      104                01/01/2013
After update my table should be like below
Sort_num     Emp_id   office      start_date
1                      101     AUS    01/01/2013
2                      101     AUS    01/01/2013
3                      101               15/01/2013
4                      103     USA    05/01/2013
5                      103               01/01/2013
6                      103    USA     05/01/2013
7                      104     FRA    10/01/2013
8                      104     FRA     10/01/2013
9                      104                01/01/2013
Thanks in advance

I do not have time to create the table with data but basically you should be able to code the following
update table a
set office = ( select office from table b where b.emp_id = a.emp_id
                                                             and     b.start_date = a.start_date
                                                             and     b.office is not null
where exists ( [same query as in set] )
and a.office is null
I believe that will do the trick.
HTH -- Mark D Powell --

How do you search for a partial match in a vector table?

Hi,
I have a program that parses some table of mine into a vector table. It has a search function in the program that is intended to search the vector table for a specified keyword that the user enters. If a match is found, it returns true. If no match is found, false is returned.
That part works great. However, I would like my program to search the vector table to try and find a PARTIAL match of the users entry, instead of looking for a complete match.
Currently my program uses the Vector method 'contains(Object elem)' to find the complete matches and that part works great. It doesn't seem to work with partial matches. Either the exact syntax of the user's entry is in the table or it isn't.
Hope I was clear enough. Any thoughts?
Cheers,
the sherlock

You might find this code of interest. It uses the same commands as mentioned previously, but wraps them into a Comparator object. Note that you can't store elements with '*' in the Vector 'v' and that you must sort the elements with Collections.sort() beforehand.
import java.util.*;
class WildcardComparator implements Comparator
    public int compare(Object o1, Object o2)
     String string1 = (String)o1;
     String string2 = (String)o2;
     if(string2.indexOf("*") != -1) {
         // take off asterik
         return wildcardCompare(string1,
                       string2.substring(0, string2.length()-1));
     return string1.compareTo(string2);
    public int wildcardCompare(String s1, String key_s) {
     String s1substring = s1.substring(0, key_s.length());
     return s1substring.compareTo(key_s);
public class wildcard
    public static void main(String[] args)
     Vector v = new Vector();
     v.add("coke");
     v.add("pepsi");
     v.add("7-up");
     v.add("a&w root beer");
     v.add("a&w cream");
     Collections.sort(v, new WildcardComparator());
     String key = "a&w*";
     int index = Collections.binarySearch(v,
                              key,
                              new WildcardComparator());
     if(index > 0)
         System.out.println("elem: " + v.get(index));
     else
         System.out.println("item not found");
     key = "c*";
     index = Collections.binarySearch(v,
                              key,
                              new WildcardComparator());
     if(index > 0)
         System.out.println("elem: " + v.get(index));
     else
         System.out.println("item not found");
}

Wich is table for match between Infoprovider and update with technical name

Thanks in advance!
Bye!
Ferdinando

Hello ,
You can check table --> RSUPDINFO table for Update rules with tech ID between Cube and InfoSources.
and other ref tables are --> RSUPDROUT / RSUPDDAT / RSUPDKEY /
--EnjoySAP
**Award credits if you are done with my answer

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

How to pull multiple lines of info from a table for a Specific Company/Address

What I would like to do is have one Table that I enter all my information on in Numbers for incoming rent like the one below. Since I have 8 spaces to rent I will have up to 96 plus rows of information to look at. But I would like to have Numbers then on separate pages is have the individual Companies have their own rent break down on a table with the Date Recieved and the amount they payed. From there on their separate page I can have the Late Charges come into play or whatever I choose.
Date
Company
Address
Rent Recieved
Jan 1, 2011
X
430
$1,100.00
Jan 3, 2011
Y
440
$1,200.00
Jan 5, 2011
Z
450
$1,300.00
Feb 1, 2011
Y
440
$1,200.00
Feb 3, 2011
X
430
$1,100.00
Feb 8, 2011
Z
450
$1,300.00
Mar 1, 2011
Z
450
$1,300.00
Mar 2, 2011
X
430
$1,100.00
Mar 5, 2011
Y
440
$1,200.00
The following table would be on the separate page with the formula (I do not know how to write) grabbing the info from the above table.
Company X Rent Recieved
Date
Rent Recieved
From the formula that one of you gracious smart people provide I could create a table for each of the Companies that rent from me on their own Tables on separate Tabs.
I know I could go to each individual Tab and write it in but I will be primarily working on my iPad and this would make it easier. I can also utilize the fresh Tables to do other calculations.

I got a soluce with no swap.
I created a new column (E)
In E2, the formula is :
=B&IF(ISBLANK(A),"",MONTH(A))
Apply Fill Down
In table of each company, I inserted a 2nd header row so that I may store the name of the company in A1.
In A3, the formula is :
=IFERROR(OFFSET(Tableau 1 :: $A$1,MATCH($A$1&ROW()-2,Tableau 1 :: $E,0)-1,0),"")
in B3, the formula is :
=IFERROR(OFFSET(Tableau 1 :: $D$1,MATCH($A$1&ROW()-2,Tableau 1 :: $E,0)-1,0),"")
Select A3:B3 then Fill Down.
That's all folks !
Yvan KOENIG (VALLAURIS, France) jeudi 19 mai 2011 17:18:32
Please :
Search for questions similar to your own before submitting them to the community
To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

HT3354 how can i use one table for reference to another

how can i use a table for a referance to another eg when i type a word in a cell, i will like it to match the word with another table then return the information in the cell i am using

you can use vlookup() (or any of the lookup family of functions) to locate an item based on a key value:
Here is an example of something you can do with two tables:
The table on the right is title "Data" and stores a list of names with age and favorite color.
The table on the left uses the value in the first column to lookup up information in the table Data
in the table on the left:
B2=IFERROR(A2&" is " & VLOOKUP(A2, Data :: A:D, 2, 0)&" years old and likes the color "& VLOOKUP(A2, Data :: A:D, 3, 0), "NOT FOUND")
I know this look complicated. so I'll break it up into smalled pieces:
first the "&" is called the concatenate operator and joins two strings. like this:
a string is a set of characters between double quotes.
so "string 1" & "string 2" becomes "string 1string2" or "Sam " & "Jones" becomes "Sam Jones"
you can use cell references instead of strings directly in which case the concatenation is performed on the contents of the cells.
so if cell A1 contains "Hi " and the cell A2 contains "There" then A1 & A2 will result in "Hi There"
so you could add the formula
A3=A1 & A2
this is short hand for select cell A3 then type everything including the A3 so that A3 contains "=A1 & A2" (omit the double quote)
OK. So the formula I provided concatenates several items together:
it concatenates A2, then the string " is " then a formula, then the string " years old and likes the color " then a formula
the two formulas (highlighted in blue) perform a lookup of the value in cell A2 in columns A thru D of the table named "Data". If if finds the value in cell A2 in the first column of the lookup range in the table Data (column A) then it returns the value from the same row but in the second or third column.
all that is in a function calld iserror() to trap the condition where the calue you enter in A2 does not exist in the table Data:
You will find the Numbers users guide and function reference helpful. You can download then from Apple here:
http://support.apple.com/manuals/#productivitysoftware

Archiving Object - Entry missing in Customizing table for object Z*********

Hello friends,
We have created a archiving object in transaction AOBJ. However when i enter this object in SARA, we get this error message.
"Entry missing in Customizing table for object Z******* "
I have matched my object with few other archiving objects and things looks similar.
Have you faced this kind of problem..
thanks
ashish

Hi,
I checked and i can see entry for ZSCS_TRAFO object in AOBJ.
But when i enter ZSCS_TRAFO, i get this error :
Entry missing in Customizing table for object ZSCS_TRAFO
Message no. BA057
Diagnosis
A function cannot be executed due to a missing table entry.
Procedure
Please create an entry for the archive object ZSCS_TRAFO with the AOBJ transaction.
However, a few other Z objects works well.
thanks
ashish

What are the Target Base Tables for FA_TAX_INTERFACE table?

Hi,
We are using "upload tax book interface" program to update the Tax Book informaiton.
For this we wanted to know all the Target Base Tables for FA_TAX_INTERFACE table (Specially for the ATTRIBUTE1-ATTRIBUTE15 columns of the interface table).
Kindly request you to help on this.
Thanks & Regards,
Satvik Patel

Well, what are you reconciling to? You are looking at something that seems to be different from your data extract, so what is that thing? My trouble shooting process is to take an asset that seems to be wrong and reconcile from the report/screen data to the extract data. You have to figure out what Oracle program is involved and what kind of SQL that the program is doing and what tables it is looking at. This could be an Oracle program error. I just ran into a problem on the Payables Posted Invoice Register report, where the total did not match my extract total. Turns out the report was wrong. If I had table records with a date/time stamp value (instead of just a date stamp value) in the accounting date field for the TO ACCOUNTING DATE value in my report request selection, those records were being dropped from the report. I reported this to Oracle support and found out that there is a patch to fix the problem (happens when cancelling an invoice) and a data script to follow to fix the historical data. So you have to keep an open mind. Yes, trying to find a reconciling issue can be very painful.
My reaction is that you are looking at the right tables. There is also a FA_DISTRIBUTION_HISTORY table that you may want to look into, that links back to the FA_DEPRN_DETAIL table. Maybe your issue lies there. At least something to look at.
John Dickey

Table for EBP users

Hello all,
I would like to distinguish EBP users from others sent from HR system. Is there any table where I can match users created in EBP and with their positions from HR.
HRP1001 is not sufficient becuse there is no difference between EBP users and other persons in HR. Even BP are created for persons in HR.
TIA
Gordan

Hi Gordan,
I don't know how you will use this information but you might be able to distinguish the users in transaction RSUSR200. Here you can see the creator of the user and it might be of help.
regards,
Kristoffer

Problem occured when create a tree table for master-detail view objects using SQL queries?

I am programming a tree table for master-detail view objects using SQL queries and these 2 view objects are not simple singel tables queries, and 2 complex SQL are prepared for master and view objects. see below:
1. Master View object (key attribute is SourceBlock and some varaible bindings are used for this view object.)
SELECT cntr_list.SOURCE_BLOCK,
        sum(
         case when cntr_list.cntr_size_q = '20'
              then cntr_list.cntr_qty
              else 0 end ) as cntr20 ,
        sum(
         case when cntr_list.cntr_size_q = '40'
              then cntr_list.cntr_qty
              else 0 end ) as cntr40 ,
         sum(
         case when cntr_list.cntr_size_q = '45'
              then cntr_list.cntr_qty
              else 0 end ) as cntr45
FROM (
    SELECT yb1.BLOCK_M as SOURCE_BLOCK,
           scn.CNTR_SIZE_Q,
           count(scn.CNTR_SIZE_Q) AS cntr_qty
    FROM SHIFT_CMR scm, SHIFT_CNTR scn, YARD_BLOCK yb1, YARD_BLOCK yb2
    WHERE
    scm.cmr_n = scn.cmr_n
    AND (scm.plan_start_dt BETWEEN to_date(:DateFrom,'YYYY/MM/DD HH24:MI:SS') AND to_date(:DateTo,'YYYY/MM/DD HH24:MI:SS')
    OR scm.plan_end_dt BETWEEN to_date(:DateFrom,'YYYY/MM/DD HH24:MI:SS') AND to_date(:DateTo,'YYYY/MM/DD HH24:MI:SS'))
    AND scm.shift_mode_c = :ShiftModeCode
    AND scm.end_terminal_c = :TerminalCode
    AND scm.start_terminal_c = yb1.terminal_c
    AND scm.start_block_n = yb1.block_n
    AND substr(scn.start_location_c,(instr(scn.start_location_c,',',1,5)+1),instr(scn.start_location_c,',',1,6)-(instr(scn.start_location_c,',',1,5)+1)) BETWEEN yb1.slot_from_n AND yb1.slot_to_n
    AND scm.end_terminal_c = yb2.terminal_c
    AND scm.end_block_n = yb2.block_n
    AND substr(scn.end_location_c,(instr(scn.end_location_c,',',1,5)+1),instr(scn.end_location_c,',',1,6)-(instr(scn.end_location_c,',',1,5)+1)) BETWEEN yb2.slot_from_n AND yb2.slot_to_n
    AND scn.status_c not in (1, 11)
    AND scn.shift_type_c = 'V'
    AND scn.source_c = 'S'
    GROUP BY yb1.BLOCK_M, scn.CNTR_SIZE_Q
) cntr_list
GROUP BY cntr_list.SOURCE_BLOCK
2. Detail View object (key attributes are SourceBlock and EndBlock and same varaible bindings are used for this view object.)
SELECT cntr_list.SOURCE_BLOCK, cntr_list.END_BLOCK,
        sum(
         case when cntr_list.cntr_size_q = '20'
              then cntr_list.cntr_qty
              else 0 end ) as cntr20 ,
        sum(
         case when cntr_list.cntr_size_q = '40'
              then cntr_list.cntr_qty
              else 0 end ) as cntr40 ,
         sum(
         case when cntr_list.cntr_size_q = '45'
              then cntr_list.cntr_qty
              else 0 end ) as cntr45
FROM (
    SELECT yb1.BLOCK_M as SOURCE_BLOCK,
           yb2.BLOCK_M as END_BLOCK,
           scn.CNTR_SIZE_Q,
           count(scn.CNTR_SIZE_Q) AS cntr_qty
    FROM SHIFT_CMR scm, SHIFT_CNTR scn, YARD_BLOCK yb1, YARD_BLOCK yb2
    WHERE
    scm.cmr_n = scn.cmr_n
    AND (scm.plan_start_dt BETWEEN to_date(:DateFrom,'YYYY/MM/DD HH24:MI:SS') AND to_date(:DateTo,'YYYY/MM/DD HH24:MI:SS')
    OR scm.plan_end_dt BETWEEN to_date(:DateFrom,'YYYY/MM/DD HH24:MI:SS') AND to_date(:DateTo,'YYYY/MM/DD HH24:MI:SS'))
    AND scm.shift_mode_c = :ShiftModeCode
    AND scm.end_terminal_c = :TerminalCode
    AND scm.start_terminal_c = yb1.terminal_c
    AND scm.start_block_n = yb1.block_n
    AND substr(scn.start_location_c,(instr(scn.start_location_c,',',1,5)+1),instr(scn.start_location_c,',',1,6)-(instr(scn.start_location_c,',',1,5)+1)) BETWEEN yb1.slot_from_n AND yb1.slot_to_n
    AND scm.end_terminal_c = yb2.terminal_c
    AND scm.end_block_n = yb2.block_n
    AND substr(scn.end_location_c,(instr(scn.end_location_c,',',1,5)+1),instr(scn.end_location_c,',',1,6)-(instr(scn.end_location_c,',',1,5)+1)) BETWEEN yb2.slot_from_n AND yb2.slot_to_n
    AND scn.status_c not in (1, 11)
    AND scn.shift_type_c = 'V'
    AND scn.source_c = 'S'
    GROUP BY yb1.BLOCK_M, yb2.BLOCK_M, scn.CNTR_SIZE_Q
) cntr_list
GROUP BY cntr_list.SOURCE_BLOCK, cntr_list.END_BLOCK
3. I create a view link to create master-detail relationship for these 2 view objects.
masterview.SourceBlock (1)->detailview.SourceBlock (*).
4. I create a tree table using these 2 view objects with master-detail relationship.
When I set default value for variable bindings of these 2 view objects and the matching records exist, tree table can work well. I can expand the master row to display detail row in UI.
But I need to pass in dymamic parameter value for variable bindings of these 2 view objects, tree table cannnot work again. when I expand the master row and no detail row are displayed in UI.
I am sure that I pass in correct parameter value for master/detail view objects and matching records exist.
Managed Bean:
        DCIteratorBinding dc = (DCIteratorBinding)evaluteEL("#{bindings.MasterView1Iterator}");
        ViewObject vo = dc.getViewObject();
        System.out.println("Before MasterView1Iterator vo.getEstimatedRowCount()="+ vo.getEstimatedRowCount());
        System.out.println("Before MasterView1Iterator ShiftModeCode="+ vo.ensureVariableManager().getVariableValue("ShiftModeCode"));
        vo.ensureVariableManager().setVariableValue("DateFrom", dateFrom);
        vo.ensureVariableManager().setVariableValue("DateTo", dateTo);
        vo.ensureVariableManager().setVariableValue("ShiftModeCode", shiftModeC);
        vo.ensureVariableManager().setVariableValue("TerminalCode", terminalCode);
        vo.executeQuery();
        System.out.println("MasterView1Iterator vo.getEstimatedRowCount()="+ vo.getEstimatedRowCount());
        DCIteratorBinding dc1 = (DCIteratorBinding)evaluteEL("#{bindings.DetailView1Iterator}");
        ViewObject vo1 = dc1.getViewObject();
        System.out.println("Before DetailView1Iterator vo1.getEstimatedRowCount()="+ vo1.getEstimatedRowCount());
        System.out.println("Before DetailView1Iterator ShiftModeCode="+ vo1.ensureVariableManager().getVariableValue("ShiftModeCode"));
        vo1.ensureVariableManager().setVariableValue("DateFrom", dateFrom);
        vo1.ensureVariableManager().setVariableValue("DateTo", dateTo);
        vo1.ensureVariableManager().setVariableValue("ShiftModeCode", shiftModeC);
        vo1.ensureVariableManager().setVariableValue("TerminalCode", terminalCode);
        vo1.executeQuery();
        System.out.println("after DetailView1Iterator vo1.getEstimatedRowCount()="+ vo1.getEstimatedRowCount());
5. What's wrong in my implementation? I don't have no problem to implement such a tree table if using simple master-detail tables view object, but now I have to use such 2 view objects using complex SQL for my requirement and variable bindings are necessary for detail view object although I also think a bit strange by myself.

Hi Frank,
Thank you and it can work.
public void setLowHighSalaryRangeForDetailEmployeesAccessorViewObject(Number lowSalary,
                                                                          Number highSalary) {
        Row r = getCurrentRow();
        if (r != null) {
            RowSet rs = (RowSet)r.getAttribute("EmpView");
            if (rs != null) {
                ViewObject accessorVO = rs.getViewObject();
                accessorVO.setNamedWhereClauseParam("LowSalary", lowSalary);
                accessorVO.setNamedWhereClauseParam("HighSalary", highSalary);
            executeQuery();
but I have a quesiton in this way. in code snippet, it is first getting current row of current master VO to determine if update variables value of detail VO. in my case, current row is possibly null after executeQuery() of master VO and I have to change current row manually like below.
any idea?
            DCIteratorBinding dc = (DCIteratorBinding)ADFUtil.evaluateEL("#{bindings.SSForecastSourceBlockView1Iterator}");
            ViewObject vo = dc.getViewObject();
            vo.ensureVariableManager().setVariableValue("DateFrom", dateFrom);
            vo.ensureVariableManager().setVariableValue("DateTo", dateTo);
            vo.ensureVariableManager().setVariableValue("ShiftModeCode", shiftModeC);
            vo.ensureVariableManager().setVariableValue("TerminalCode", terminalCode);
            vo.executeQuery();
            vo.setCurrentRowAtRangeIndex(0);
            ((SSForecastSourceBlockViewImpl)vo).synchornizeAccessorVOVariableValues();

Tables for variance calclation

Hi Experts,
My Client has a different requirement for variance calculation.
Client want the Production order variance to be calculated based on their budgeted cost and not with reference to Target cost which is again based on Standard cost. Client requires to valuate the cost of Fert and Halb items based on their budgeted cost for the variance calculation ONLY.They want a seperate report for Management information and mainly concerned with Material related variance.
Now to start with, I entered prices of Raw material (as said to be the budgeted price) in planned price 1 in Costing Tab 2 of material master for all items defined in BOM. Made a seperate Costing variant and valuation variant to consider the Planned price 1 for valuation.
With CK40N, calculated the cost of Fert and HALB items in Planned price1. Now I want to use this new cost i.e. Planned price 1 to calculate Target cost in production order calculation of variances i.e. price, Quantity, Mix,Usage etc.
My queries are as follows...
1) Am I moving in a right direction and whether the approach is correct? If No, then request you to guide me any other method to calculate the cost as per client's requirement.
2) If the answer to obove is yes, then requesting you to guide what should be the next step?
3) I want to know the table names where the values of this new cost is stored so that I can capture the values as per cost component structure and can be used for variance calculation. I have already checked the Tables KEEO and KEPH but the figures are not matching.
4) Also let me know the Table names for actual cost of production order.
Regards,
makrand

HI,
Ur Approch is correct and The tables KEKO and KEPH are absolutely correct. It must match.
AUFM is the table for fetching the values of production order.
once these things are ready, you can get the abaper to write the report to find the variance between KEKO and AUFM
Hope my answer helps!~
Vijay

Error in flex item, combinations table for this flexfield has more 1 entry

HI OAF Gurus,
I setup a flex item with the following attributes:
ID = CostAllocationKFF
Item Style = flex
View Instance = XXPerAsgDetailsVO
Rendered = true
Appl Short Name = PAY
Name = COST
Type = key
Segment List = XXPAY_COST_ALLOCATION|Company|Cost Centre
In my controller, I have the following code in processRequest to bind the KFF against the CostAllocationKFF item:
String costFlexStrucCode = "XXPAY_COST_ALLOCATION";
boolean flag1 = false;
OAKeyFlexBean oacostallockeyflexbean = (OAKeyFlexBean)webBean.findIndexedChildRecursive("CostAllocationKFF");
if(oacostallockeyflexbean != null)
oacostallockeyflexbean.useCodeCombinationLOV(flag1);
oacostallockeyflexbean.setCCIDAttributeName("CostAllocKeyflexId");
oacostallockeyflexbean.setStructureCode(costFlexStrucCode);
Now, at processRequest it is picking up the right segment values. However, when I dont update the segments and I hit a button that will eventualy call processFormRequest, it is giving me the following error,
"The combinations table for this flexfield contains more than one entry that matches the entered values. Inform your system administrator that the combination identified by the number 6419 is duplicated."
Is there anything that I'm missing? What should I do to refrain from such error happening? I also have a flex item for people group but it is not giving me the same error message. Please advise. Thank you very much.

can someone help shed light on this? I'm still trying to find out what's causing this issue. Thanks!

How do we use Data rules/error table for source validation?

How do we use Data rules/error table for source validation?
We are using OWB repository 10.2.0.3.0 and OWB client 10.2.0.3.33. The Oracle version is 10 G (10.2.0.3.0). OWB is installed on Linux.
I reviewed the posting
Re: Using Data Rules
Thanks for this forum.
I want to apply data rules to source table/view and rule violated rows should go to defined error table. Here is an example.
Table ProjectA
Pro_ID Number(10)
Project_name Varchar(50)
Pro_date Date
As per above posting, I created the table in object editor, created the data rule
NAME_NOT_NULL (ie project name not null). I specified the shadow table name as ProjectA_ERR
In mapping editor, I have projectA as source. I did not find error table name and defined data rules in table properties. It is not showing up the ERR group in source table
How do we bring the defined data rules and error table into mapping?
Are there any additional steps/process?
Any idea ?
Thanks in advance.
RI

Hi,
Thanks for your reply/pointer. I reviewed the blog. It is interesting.
What is the version of OWB used in this blog?
After defining data rule/shadow table, I deployed the table via CC. It created a error table and created the all the source coulmns in alphabatical order. If I have the primary key as 1st coulmn (which does not start with 'A') in my source, it will apprear middle of of columns in error table.
How do we prevent/workaround this?
If I have source(view) in sch A, how do we create Error table in Sch B for source(view)?
Is it feasible?
I brought the error table details in mapping. Configured the data rules/error tables.
If I picked up 'MOVE TO ERROR' option, I am getting "VLD-2802 Missing delete matching criteria in table. the condition is needed because the operator contain at least one data rule with a MOVE TO ERROR action"
On condition Loading - I have 'All constraints' for matching criteria.
I changed to "no constraints' still I get the above error.
If I change to 'REPORT' option instead of 'MOVE TO ERROR' option, error goes off.
Any idea?
Thanks in advance.
RI

Table for Intercompany GL Matching

Similar Messages

Maybe you are looking for