"Payables Open Interface Purge" Program

Hi Guys,
In our production system, it takes 3 minutes to open "Open Interface Invoices" form (AP Manager>Invoices>Entry>Open Interface Invoices). So what should we do so as to avoid this.
I was thinking to delete data from two tables (AP_INVOICES_INTERFACE & AP_INVOICE_LINES_INTERFACE) based on certain crieterions. Like all the records which have been successfully imported i.e. with status='PROCESSED' can be deleted. So, I can achieve this using two methods:
1. Manually using SQL Delete statement. i.e.
DELETE FROM AP_INVOICES_INTERFACE WHERE status='PROCESSED';
DELETE FROM AP_INVOICE_LINES_INTERFACE
WHERE invoice_id IN (SELECT invoice_id FROM AP_INVOICES_INTERFACE WHERE status='PROCESSED');
2. Or I can use "Payables Open Interface Purge" Program.
I ran this program for my specific source, and checked the count from tables but the result is the same. This means this program has not deleted any of the processed records from these two tables for the particular source.
What can be the reason for this? Please suggest me on this.
Thanks a lot!
Regards,
Sumir Chawla

Hi,
Thanks for your reply friends!
I ran the program for some source. It completed successfully, log shown below:
MSG-00001: (Import_purge 1) Check control table for the purge process
MSG-00001: (Check_control_table 1) Lock the control table
MSG-00003: (Check_control_table 2) Fetch import_requests
MSG-00007: (Check_control_table 5) Insert record into control table
MSG-00008: (Check_control_table 6) Commit
MSG-00002: (Import_purge ) Deleting records in interface tables...
MSG-00008: (Import_purge 5) Commit to the database
MSG-00010: (Import_purge 7) Delete the previous record in ap_interface_controls
But when I checked both the tables ap_invoices_interface and ap_invoice_lines_interface from backend, the records which should not exist for that particular source and which imported successfully (as purge all is 'No') are still existing in the tables. If I am correct, after successfull run, records should not exist for the source which have status "processed". Please correct me if I am wrong. I think I should log SR.
Thanks & Regards,
Sumir Chawla

Similar Messages

  • Payables Open Interface Purge completes with error "Invalid Cursor"

    Hello,
    I'm trying to run Payables Open Interface Purge (version 115.8) and get an invalid cursor error in the beforereport trigger. Does anyone know the cause and remedy of this? A portion of the log is below. I've looked at the cursor and everything looks fine to me.
    MSG-00001: (Import_purge 1) Check control table for the purge process
    MSG-00001: (Check_control_table 1) Lock the control table
    MSG-00003: (Check_control_table 2) Fetch import_requests
    MSG-00004: (Check_control_table 3) Check concurrent program status
    MSG-00999: FUNCTION GET_REQUEST_STATUS ERROR, Reason:
    MSG-00999: FND_CONCURRENT.GET_REQUEST_STATUS<-Check_control_table<-Import_purge<- Before report trigger <- APXIIPRG
    MSG-00999: check_control_table<-Import_purge<- Before report trigger <- APXIIPRG
    MSG-00999: (Import_purge 1) Check control table for the purge process
    MSG-00999: Delete record in control table..
    MSG-00999: ORA-01001: invalid cursor
    REP-1419: 'beforereport': PL/SQL program aborted.
    Thank you.

    I'm trying to run Payables Open Interface Purge (version 115.8) and get an invalid cursor error in the beforereport trigger. Does anyone know the cause and remedy of this? A portion of the log is below. I've looked at the cursor and everything looks fine to me.
    MSG-00001: (Import_purge 1) Check control table for the purge process
    MSG-00001: (Check_control_table 1) Lock the control table
    MSG-00003: (Check_control_table 2) Fetch import_requests
    MSG-00004: (Check_control_table 3) Check concurrent program status
    MSG-00999: FUNCTION GET_REQUEST_STATUS ERROR, Reason:
    MSG-00999: FND_CONCURRENT.GET_REQUEST_STATUS<-Check_control_table<-Import_purge<- Before report trigger <- APXIIPRG
    MSG-00999: check_control_table<-Import_purge<- Before report trigger <- APXIIPRG
    MSG-00999: (Import_purge 1) Check control table for the purge process
    MSG-00999: Delete record in control table..
    MSG-00999: ORA-01001: invalid cursor
    REP-1419: 'beforereport': PL/SQL program aborted.11i: Payables Open Interface Invoice Import Troubleshooting Guide (APXIIMPT) [ID 107628.1] -- 3. Open Interface Import Purge Fails with ORA-01001: Invalid Cursor
    Thanks,
    Hussein

  • Facing issues in Payables Open Interface Import Program

    Hi,
    We have a requirement of calling Payables Open Interface Import Program from Pl/sql package.
    Invoices are getting created.
    But the issue is when we query our invoice from invoice workbench and we try to view  the record history (help->record history)
    We are getting the error as ‘fdxwho failed due to ORA-01403’.
    The code is
    l_num_req_id :=
                fnd_request.submit_request
                                          (application      => 'SQLAP',
                                           program          => 'APXIIMPT',
                                           argument1        => fnd_global.org_id,
                                           -- org_id
                                           argument2        =>l_chr_source, 
                                           -- Invoice source
                                           argument3        => NULL,
                                           argument4        => l_chr_batch_name,
                                           -- Batch Name
                                           argument5        => NULL,
                                           argument6        => NULL,
                                           --  Hold Raeson
                                           argument7        => NULL,    -- GL Date
                                           argument8        => 'N',
                                           argument9        => 'N',
                                           argument10       => 'N',
                                           argument11       => 'N',
                                           argument12       => '1000',
                                           argument13       => fnd_global.user_id,
                                           argument14       => fnd_global.login_id
    Regards
    Suresh

    Hi,
    Please review notes:
    APP-01564 ORA-01403 in FDXWHO In Any Payables Form (Doc ID 1077762.6)
    "APP-FND-01564 ORACLE error 1403 in fdxwho" in Record History (Doc ID 879528.1)
    Thanks &
    Best Regards,

  • Payables Open Interface Import program is not Importing the Invoices

    Hi All,
    We are trying to create new invoices (SUM_DIF) based on the Foreign currency gain/Loss amounts. But payables open interface import program is rejecting all invoices with the rejectionr code as "No Invoice Lines, Atleast one invoice line is required".
    But when we check in the interface tables we have invoices as well as the corresponding lines for those invoices. This issue is happening in 12.0.6
    Any one faced this similar issue earlier? Any help is highly appreciated.
    Thanks,
    Rama Krishna.

    Hi,
    No issues for me on Payables Open Invoice Interface with 12.0.6 - and yes make sure you match up the invoice_id on invoice, lines interface tables.
    Regards,
    Gareth

  • Payables Open Interface Import program is getting failed

    REP-0004: Warning: Unable to open user preference file.
    MSG-00999: ORA-03113: end-of-file on communication channel
    ORA-01403: no data found
    REP-1401: 'beforereport': Fatal PL/SQL error occurred.
    ORA-03113: end-of-file on communication channel
    REP-0069: Internal error
    REP-57054: In-process job terminated:Terminated with error:
    REP-1401: MSG-00999: ORA-03113: end-of-file on communication channel
    ORA-01403: no data found
    REP-1401: 'beforereport': Fatal PL/SQL error occurred.
    ORA-03113: end-of-file on communication channel

    Hi Pravin,
    Thanks, In trace file I found below error:
    [2014/10/30 7:26:26:227] State 56016 (JobManager:updateJobStatus): Job 1 status is: Running the report Running before report trigger
    [2014/10/30 7:26:26:227] Debug 50103 (JobManager:notifyWaitingJobs): Master job 1 notify its duplicated jobs.
    [2014/10/30 7:26:26:228] Debug 50103 (JobManager:updateJobStatus): Finished updating job: 1
    [2014/10/30 7:26:26:228] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_DEBUG_SWITCH
    [2014/10/30 7:26:26:228] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_DEBUG_SWITCH
    [2014/10/30 7:26:26:228] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_BATCH_NAME
    [2014/10/30 7:26:26:228] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_BATCH_NAME
    [2014/10/30 7:26:26:228] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_GL_DATE
    [2014/10/30 7:26:26:228] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_GL_DATE
    [2014/10/30 7:26:26:228] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_HOLD_CODE
    [2014/10/30 7:26:26:228] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_HOLD_CODE
    [2014/10/30 7:26:26:229] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_HOLD_REASON
    [2014/10/30 7:26:26:229] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_HOLD_REASON
    [2014/10/30 7:26:26:229] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_COMMIT_CYCLES
    [2014/10/30 7:26:26:229] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_COMMIT_CYCLES
    [2014/10/30 7:26:26:229] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_SOURCE
    [2014/10/30 7:26:26:229] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_SOURCE
    [2014/10/30 7:26:26:229] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_GROUP_ID
    [2014/10/30 7:26:26:229] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_GROUP_ID
    [2014/10/30 7:26:26:229] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_CONC_REQUEST_ID
    [2014/10/30 7:26:26:230] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_CONC_REQUEST_ID
    [2014/10/30 7:26:26:230] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_ORG_ID
    [2014/10/30 7:26:26:230] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_ORG_ID
    [2014/10/30 7:26:26:230] APP 50103 (C Engine): 07:26:26  APP  (  Database Column          P_SUMMARY_FLAG
    [2014/10/30 7:26:26:230] APP 50103 (C Engine): 07:26:26  APP  )  Database Column          P_SUMMARY_FLAG
    [2014/10/30 7:26:26:230] PLSQL 50103 (C Engine): 07:26:26  PLS  (  Function:       beforereport
    [2014/10/30 7:27:55:427] Error 50103 (C Engine): 07:27:55  MSG MSG-00999: ORA-03113: end-of-file on communication channel
    ORA-01403: no data found
    [2014/10/30 7:27:55:429] PLSQL 50103 (C Engine): 07:27:55  PLS  )  Function:       beforereport
    [2014/10/30 7:27:55:429] Error 50103 (C Engine): 07:27:55  ERR REP-1401: 'beforereport': Fatal PL/SQL error occurred.
    [2014/10/30 7:27:55:432] Error 50103 (rwfdt:rwfdtprint): 07:27:55  ERR Error occurred sending Job output to cache
    [2014/10/30 7:27:55:433] Error 50103 (rwfdt:rwfdtfl_FreeDistList): running
    [2014/10/30 7:27:55:433] Error 50103 (rwfdt:rwfdtfl_FreeDistList): quit
    [2014/10/30 7:27:55:441] State 56016 (JobManager:updateJobStatus): Job 1 status is: Terminated with error:
    REP-1401: MSG-00999: ORA-03113: end-of-file on communication channel
    ORA-01403: no data found
    REP-1401: 'beforereport': Fatal PL/SQL error occurred.

  • Payables Open Interface Import getting errors out

    Hello All,
    I am trying to run "Payables Open Interface Import" program to upload the invoice but the program is getting error out, in the log file at the end i am getting the below error:
    (Insert ap inv dists 1a) Inside the insert function
    (Insert ap inv dists 1) Insert into ap_invoice_distributions
    (Insert ap inv dists 1) Insert into ap_invoice_distributions
    ORA-00001: unique constraint (AP.AP_INVOICE_DISTRIBUTIONS_U1) violated
    Insert_ap_inv_dists<-Create_lines<-Import_invoices<- Before report trigger
    (Create Lines 22) Insert into ap_invoice_distributions
    create_non_item_lines<-Import_invoices<- Before report trigger
    Any one faced this kind of issue?
    any suggestions to resolve this.
    Thanks & Regards
    Aboothahir

    Pl post details of OS, database and EBS versions.
    Pl see these MOS Docs
    Payables Open Interface Error ORA-00001: unique constraint (AP.AP_INVOICE_DISTRIBUTIONS_U1) violated          (Doc ID 357784.1)
    APXIIMPT Payables Open Interface Import Fails ORA-00001          (Doc ID 353052.1)
    Unique Constraint Violated Importing Invoices With Multi Line Distribution Set          (Doc ID 386323.1)
    HTH
    Srini

  • Payables Open Interface Import

    Currently the AP folks run the 'Payables Open Interface Import' for certain types of source's.
    I am trying to run the 'Payables Open Interface Import' request for a newer source. I am getting the following error:
    REP-1419: 'beforereport': PL/SQL program aborted.
    My parameters are almost the same (only the source name and the batch name are different) as what the AP folks are using. Their requests completed successfully...mine did not. How would I know which part of the before report is causing it to fail?
    Thanks,
    Chiru

    The before report trigger error does occur for n number of reasons...some of the solutions could be
    1. Setting up the debug/summarized params to Y or
    2. Two payables open interface import programs running at the same time and due to non-incompatibility setups, one of them is getting errored out. Try setting up incompatibility and this error will go away - the only problem with this approach is that if this program needs to run on frequent basis, then one will wait on other to complete and consume lot of time.
    3. Try to increase threads of concurrent manager under which this program runs for better resouce management.
    4. Check the normal AP side setups such as tax code definition, supplier site 'pay site flag' etc --Although before report error occurs at the place in rdf where these checks are yet not done but thought to share with you if it helps
    Thanks
    Girish

  • Problem with payables open interface import-unable to pick invoice data

    Hi,
    I have put the Interface data in two staging table and then moved them to AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables.
    Code:
    insert into XXWU_AP_INVOICES_INTERFACE (
    invoice_id,
    invoice_num,
    vendor_id,
    vendor_site_id,
    vendor_site_code,
    invoice_amount,
    INVOICE_CURRENCY_CODE,
    invoice_date,
    DESCRIPTION,
    PAY_GROUP_LOOKUP_CODE,
    source,
    org_id,
    OPERATING_UNIT
    values (
    ap_invoices_interface_s.nextval,
    'INV345DJ',
    '3317',
    '14335',
    'ACH NY1',
    1200.00,
    'USD',
    to_date('01-31-2010','mm-dd-yyyy'),
    'This Invoice is created for test purpose',
    'WUFS SUPPLIER',
    'Manual Invoice Entry',
    81,
    'WU_USD_OU'
    insert into XXWU_AP_INVOICE_LN_INTERFACE (
    invoice_id,
    invoice_line_id,
    line_number,
    line_type_lookup_code,
    amount,
    org_id
    values (
    ap_invoices_interface_s.currval,
    ap_invoice_lines_interface_s.nextval,
    1,
    'ITEM',
    1200.00,
    81
    INSERT INTO AP_INVOICES_INTERFACE (SELECT * FROM XXWU_AP_INVOICES_INTERFACE);
    INSERT INTO AP_INVOICE_LINES_INTERFACE (SELECT * FROM XXWU_AP_INVOICE_LN_INTERFACE);
    I can very much see the data in Open Interface Invoices(Front End). But when I run the payables open interface import program with correct Operating Unit, Source and Batch Name, the program unable to pick the data from the interface tables and unable to create a invoice.
    Note:
    1] The program run successfully everytime, but there is no output in the output file.
    2] In the Log file One Message is there saying 'Zero(0) invoices were created during the process run.'
    3] All the initail setup is right, i think, because I ran the same program few days back and it was working fine and the invoices were created at that time. Now what is going wrong I am unable to figure it out.
    Please help ASAP.Thanks in Advance
    DJ Koch.
    Edited by: DJKOCH on 17 Aug, 2010 9:51 PM

    Can you run the program - Payables Open Interface Import with Debug mode set to Yes.
    Once the program completes sucessfully verify the log file of the program and try to find out if there are any invoices which is causing the exceptions.
    Also confirm that the invoices which are in the AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables are of the correct period in which you are trying to create the invoices.
    Hope this helps.
    Thanks and Regards
    Manish Jain.

  • Problem with Payables Open Interface Import

    We have a third party's software which uploads invoices into the OraFin's (11.5.9) AP_INVOICES_INTERFACE and AP INVOICES_LINES_INTERFACE tables. Then we run PAYABLES OPEN INTERFACE IMPORT PROGRAM, and Invoice_id in AP_INVOICES_ALL has different value then we just had before in interface tables.
    The sequence has replaced the Invoice_id with new one instead of just to transfer it to the base table (AP-Invoices_All) only.
    Is there any way to avoid the change of the given Invoice_id?
    Thanks for your prompt answer, Gurus :).

    The sequence has replaced the Invoice_id with new one instead of just to transfer it to the base table (AP-Invoices_All) only.Is there any way to avoid the change of the given Invoice_id?
    No.
    This is standard functionality. Invoice import program regenerates the invoice_id from sequence everytime the invoice is imported.
    Thanks
    Nagamohan

  • Payables Open Interface Import pass distribution set for header?

    Hi all,
    i'm using OEBS 12.1.3. I want to insert data into payables interface tables to create invoice via back-end. Is it possible to pass data for the DISTRIBUTION SET on header level? I searched in the table AP_INVOICES_INTERFACE but no such column founded. I'm able to pass info for the distribution on the line level...
    Any ideas?
    Thanks in advance,
    Bahchevanov.

    The before report trigger error does occur for n number of reasons...some of the solutions could be
    1. Setting up the debug/summarized params to Y or
    2. Two payables open interface import programs running at the same time and due to non-incompatibility setups, one of them is getting errored out. Try setting up incompatibility and this error will go away - the only problem with this approach is that if this program needs to run on frequent basis, then one will wait on other to complete and consume lot of time.
    3. Try to increase threads of concurrent manager under which this program runs for better resouce management.
    4. Check the normal AP side setups such as tax code definition, supplier site 'pay site flag' etc --Although before report error occurs at the place in rdf where these checks are yet not done but thought to share with you if it helps
    Thanks
    Girish

  • How to get unique Batch Name for AP Open Interface Import Program

    Hi,
    We have enabled the invoice batch controls i.e. the profile option 'AP: Use Invoice Batch Controls' set to Yes.
    We have an interface with some system from where we receive a data file that has AP invoices. The invoices are loaded into staging table, and finally into AP invoice interface tables. After this the AP Open interface import is run.
    The relevant programs are in a concurrent request set and are executed every day.
    The issue is with the 'Batch Number' parameter of the Payables Open Interface Import Program. If I enter some text as the batch number, the Batch gets created with that name only. As such we need the Batch number to be unique for each job run.
    Oracle help says "If the AP: Use Invoice Batch Controls profile option is enabled and if you provide no value for this parameter then the system provides a value for you. The value the system provides is the concatenation of the Source and a unique sequential number. For example, ERS: 1234".
    However the problem is the Batch Name Parameter is mandatory, and cannot be left NULL.
    Has any one faced this issue earlier? Am I missing any setup or step?
    Any inputs in this regard would be highly appreciated!
    Best regards,
    Anand

    The proper Oracle suggested method would be to put a wrapper program around your request set that determines the batch name.
    The easier (abet less supported) method:
    CREATE OR REPLACE TRIGGER custom.coop_ap_batches_all_insert
    BEFORE
    INSERT
    ON ap.ap_batches_all
    REFERENCING NEW AS NEW OLD AS OLD
    FOR EACH ROW
    BEGIN
    -- to update batch name...
    -- created so that the nightly batches can have unique names by date
    -- nightly batches will be created with their simple name
    -- IE VIR, DI, MI, etc... this trigger will rename them
    -- to YYYY-MM-DD-VIR, YYYY-MM-DD-DI, YYYY-MM-DD-MI, etc...
    IF LENGTH(TRIM(:new.batch_name)) < 4 THEN
    :new.batch_name := TO_CHAR(SYSDATE,'YYYY-MM-DD') || '-' || :new.batch_name;
    END IF;
    :new.batch_name := UPPER(:new.batch_name);
    END;
    /

  • Payable Open Interface Import

    Hi All,
    I am trying to run payable open interface import program to upload 'STANDARD' invoice.Problem is that when i run 'PAYABLE OPEN INTERFACE IMPORT'
    program it fetch record from interface table, but does not create invoice in oracle and its also not showing the rejection reason in 'AP_INTERFACE_REJECTION'.
    I also found a doc regarding this issue on metalink with id 1139837.1 , but the solution in this doc is already working.
    Please let me know if you have a workaround.
    Oracle Version--R12.1.3
    Database Version--11g

    Hello
    Please elaborate on the solution
    I am facing the same issue with R12.1.3 and 11g database.
    I have checked the metalink note and that is not applicable to me as well.
    I have turned on the debug switch and yet the failed invoices don't appear on the rejection report
    Regards
    Ariv

  • Prevent AP Invoices being picked by POII (Payables Open Interface Import)

    Hi,
    We have a requirement to prevent the AP Invoices in Payable Open Interface table from being picked by POII (Payables Open Interface Import) program.
    Kindly provide your inputs on this.
    Thanks & Regard,
    Satvik Patel

    That is correct, the documentation does specify not to populate a value into this field, however there is no harm in doing so.
    Alternatively, if you are not using the Payables Open Interface Workflow, then you could either populate a value of "Y" or "S" into the WORKFLOW_FLAG column, to prevent the invoices from getting imported.
    Or you could just supply a dummy value for the org_id column in the interface table
    Edited by: pillair on Aug 1, 2012 1:10 AM

  • JAEHYLEE  (R11i AP)   Payables Open Interface Import  REJECT CODE:NO TERMS

    Purpose
    Payables Open Interface Import REJECT CODE:NO TERMS
    Symptoms
    'EDI' Source로 invoice를 import할때 Payables Open Interface Import program 이 error로 종료된다
    정상적인 에러 No Terms로 출력이 되나 , 데이타 상에는 아무 이상이 없으며
    debug log file 의 reject code는 NO TERMS INFO라고 출력된다
    REJECT CODE:NO TERMS INFO
    CauseThe import program in procedure v_check_invalid_terms does not have exception handling. So, when ever it has exceptions like no_data_found or too_many_rows control was returning to the final exception block and the procedure was returning false to the calling procedure. Hence the error instead of Reject reason.
    Bug 4704918 - APXIIMPT DOESN'T REJECT INVOICES WITH INCONSISTENT TERMS.
    Solution
    AP.N이상에서 patch 4755024를 적용
    Please apply Patch 4755024 - 1OFF:4704918:AP.N:FP.G:11.5.10:APXIIMPT DOESN'T REJECT INVOICES
    Reference
    Note 359089.1

    Have you customized/setup the Project Accounting Workflow builder. You need to do some setup for this workflow builder so that the project accounts can be derived properly.

  • Payable open interface import Issue!

    Hello:
    I want to insert the Debit Memo invoice type through Payable open interface import API, But Payable open interface import program throw the error named is Invalid Inv type lookup code.
    I read out the Oracle Paybales documentation, Oracle does not support the DEBIT invoice type it only supports Standard and Credit type.
    Is there any possibility can we insert the DEBIT type from Payable open interface import program?.
    Please reply me ASAP.
    Thank you.
    Zeeshan

    Thank you Sanjit!
    Sanjeet Can you tell me the steps of How to register my stored procedure in APPS and how can I set my concurrent request.
    Please I need a steps.
    Regards
    Zeeshan

Maybe you are looking for

  • I'm not crying. Is there a way to install Mountain Lion on a bootable disk on latest iMac cuz mine shipped without an OS?

    I could cry right now. After decades of being an Apple fan, something is happening for the worse and issues with every Apple product I own 2 iphones, 2 iMacs, 15" Macbook Pro, and iPad Mini (no issues here, just slow connecting to App Store and can n

  • Acquistion Value Negative in Area 01 while posting Goods Receipt (MIGO)

    While posting a Goods Receipt am facing the error Acquistion Value Negative in Area 01. The related Purchasing Document has an Account Assignment as AUC. I have checked the Asset Master of that AUC. In the Depreciation Areas Tab when I am trying to p

  • Why can't i connect to any gamecenter on my iPad?

    Why can't i connect to any gamecenter on my iPad? When i play,  i use my gamecenter to play with my friends. But it won't work! And sometimes when i play a game, my screen get out of the game. I really need help to fix this! And i use iOS 7 on a iPad

  • Installing iTunes on Windows Vista Ultimate (32bit)

    I can't get the latest version of iTunes to install on my Vista machine (which is part of a Windows Server domain). It says the app is unsigned, pops up the various alert boxes asking me what to do. Selecting the options that allow installation and..

  • Error on CIF activation

    Dear APO experts.. While activating CIF IM I am getting following error and the material is not trasferred to APO "System: APOCLNT660  User: ZPAPOTEST   *Function/Q/SAPAPO/CIF_PROD_INBOUND* *Text: Too many parameters specified with PERFORM* As I was