Difference between AP Operational Status and Registered Controller

When reviewing the AP Details page in Prime there are two fields I'm not sure what they mean specifically:
1) Operational Status - Registered
2) Registered Controller - Not Associated
Any clarity or document references would be greatly appreciated.           

This is in CPI viewing the AP Details tab.
The only valid values for Operational Status are Registered/Not Registered.
The only valid values for Registered Controller are Associated/Not Associated
The IP address is not a valid input.
It is still unclear to me what the specific and fuctional differences and impacts are between Operational Status and
Registered Controller? How do the values of each impact the client device?
Thank You.

Similar Messages

  • The difference between the QM status and total status of a request?

    Hi Experts,
    I have some confusion about the concept of the status of a request. In the data target management window, we have QM status and technical status of a request, and in the monitor, we have total status of the request. Can somebody tell me the difference between the three. Please give me some detailed info about this or provide me some document regarding this. your great help will be highly appreciated.
    Eileen

    QM status can be edited..but technical status cannot be edited..
    in the monitor..only total status can be edited..
    please see this link..gives the required info..
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a663ce07211d2acb80000e829fbfe/frameset.htm
    Vishvesh

  • Re: DIfference between Schemas, PCRS' FUnctions and Operations

    Dear SAPExperts,
    Can anybody pls tell me what is difference between Schemas, PCRS' Functions and Operations.
    Thanx in advance
    Regards
    Aniruddha

    Hi Aniruddha
    When the payroll driver is executed (for ex: PC00_M40_CALC for INDIA is executed) the schema IN00 (standard schema) is executed and it calls certain functions (functions may use Rules. Rules contain Operation) and also subschemas.
    Functions could be of four types
    1. Performing some payroll computations (E.g. INEPF function calculates the PF amount of an employee during payroll run)
    2. Calling rules (E.g. P0045 function calls a rule INLN to compute the loan details of a personnel number).
    3. Getting data from Infotypes (E.g. P0581 will get the data from Infotype-581 for payroll processing).
    4. For some decisions. (E.g. IF & ENDIF function is used to execute as per the true and false decisions) etc.
    When the PY is executed SAP uses lot of Internal Tables to store data and also provides data to other internal tables.
    The read and change access to Internal Tables is enabled using functions that are executed in a personnel calculation schema and using operations that are executed in personnel calculation rules.
    The following is just an attempt to provide some info on how Functions are processed during the PY Run. For ex: (functionality of subschema XIN0 and INBD)
    1. INITIALIZATION OF PAYROLL: When the Payroll is executed first the subschema XIN0 is called,   This subschema comprises the following main steps:
    I.     Specify program type (payroll or evaluation)
    II.     Set switch for database updates (YES/NO) all database updates are controlled via this switch (otherwise simulation)
    III.     Only infotypes from the HR master record which apply to the selected personnel number are read.
    IV.     All Time Management infotypes are imported.
    V.     Specify check against control record PA03 (test or live).
    2. READ BASIC DATA: Once the Initialization of Payroll is successful, the subschema INBD is called. This subschema reads the Basic data of an employee who is there in the Payroll execution. Basic Data includes, determining Employee Name, Reading Work Center/Basic Pay Data, Setting Financial Year Dates and Allowance Grouping Tables, Reading Previous Employment Tax Details, Reading Housing (HRA/CLA/COA), Reading Exemptions, Reading Income from Other Sources, Reading Section 80 Deductions, Reading Investment Details (Sec 88), Reading Provident Fund Contributions, Reading Other Statutory Deductions, Reading Car and Conveyance, Reading Long Term Reimbursements, Read ID Details. Function GON checks whether all the master data has been imported, no further processing of schema will occur unless certain data is present.
    The Subschema INBD calls the following functions in order to read the Basic Data:
    ENAME :
    Function ENAME reads the last valid name of the employee in the payroll period. The formatting used for the country in question is used when displaying this name.
    WPBP
    If an employee receives a pay increase within a payroll period, the Basic Pay infotype (0008) is changed and delimited as of a specific date. Two data records exist for one payroll period.
    During payroll, the system writes the Basic Pay wage type to the results table with two different indicators. These split indicators are a link to the WPBP table that contains the relevant values. The system takes into consideration both data records for the corresponding partial periods when calculating remuneration.
    ININI
    P0580
    P0581
    P0582
    P0584
    P0585
    P0586
    P0587
    P0588
    P0583
    P0590
    P185I
    GON :
                    Function GON checks whether all the master data has been imported. No further processing of the schema will occur unless certain data is present. Checking procedures vary from country to country. There must always, however, be a work center (P007).
    [Def. of Functions, Rules and Operations (copied from Raju's answer)
    Schema is a collection of functions
    A Rule is a collection of operations.
    An operation is a very basic piece of logic that is used, mostly, to manipulate wage types
    Best Regards
    Reddy

  • Difference between cancel_flag IS NULL and cancel_flag ='N'

    Hi ,
    Please clarify Difference between cancel_flag IS NULL and cancel_flag ='N' in PO Headers .
    Because from front end cancel check box is unchecked in abobe both the cases . We can see cancel check box status only in Help>Diagnostics>Examine .
    Thanks in Advance
    Kiran

    Hi Kiran,
    The is no difference between cancel_flag with 'null' and 'N' but cancel field contain Null if it is generated through auto create and it contains 'N' if Purchase order raised without PR .
    I hope you understand.
    Regards,
    Sravani.M
    Edited by: 855855 on Nov 9, 2012 5:49 AM

  • What are differences between the target tablespace and the source tablespac

    The IMPDP command create so manay errors. But the EXAMPLE tablespace is transported to the target database successfully. It seems that the transported tablespace is no difference with the source tablespace.
    Why create so many errors?
    How to avoid these errors?
    What are differences between the target tablespace and the source tablespace?
    Is this datapump action really successfull?
    Thw following is the log output:
    [oracle@hostp ~]$ impdp system/oracle dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
    Import: Release 10.2.0.1.0 - Production on Sunday, 28 September, 2008 18:08:31
    Copyright (c) 2003, 2005, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Master table "SYSTEM"."SYS_IMPORT_TABLESPACE_01" successfully loaded/unloaded
    Starting "SYSTEM"."SYS_IMPORT_TABLESPACE_01": system/******** dumpfile=user_dir:demo02.dmp tablespaces=example remap_tablespace=example:example
    Processing object type TABLE_EXPORT/TABLE/TABLE
    ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
    CREATE TABLE "OE"."CUSTOMERS" ("CUSTOMER_ID" NUMBER(6,0), "CUST_FIRST_NAME" VARCHAR2(20) CONSTRAINT "CUST_FNAME_NN" NOT NULL ENABLE, "CUST_LAST_NAME" VARCHAR2(20) CONSTRAINT "CUST_LNAME_NN" NOT NULL ENABLE, "CUST_ADDRESS" "OE"."CUST_ADDRESS_TYP" , "PHONE_NUMBERS" "OE"."PHONE_LIST_TYP" , "NLS_LANGUAGE" VARCHAR2(3), "NLS_TERRITORY" VARCHAR2(30), "CREDIT_LIMIT" NUMBER(9,2), "CUST_EMAIL" VARCHAR2(30), "ACCOUNT_MGR_ID" NU
    ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
    ORA-39117: Type needed to create table is not included in this operation. Failing sql is:
    CREATE TABLE "IX"."ORDERS_QUEUETABLE" ("Q_NAME" VARCHAR2(30), "MSGID" RAW(16), "CORRID" VARCHAR2(128), "PRIORITY" NUMBER, "STATE" NUMBER, "DELAY" TIMESTAMP (6), "EXPIRATION" NUMBER, "TIME_MANAGER_INFO" TIMESTAMP (6), "LOCAL_ORDER_NO" NUMBER, "CHAIN_NO" NUMBER, "CSCN" NUMBER, "DSCN" NUMBER, "ENQ_TIME" TIMESTAMP (6), "ENQ_UID" VARCHAR2(30), "ENQ_TID" VARCHAR2(30), "DEQ_TIME" TIMESTAMP (6), "DEQ_UID" VARCHAR2(30), "DEQ_
    Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
    . . imported "SH"."CUSTOMERS" 9.850 MB 55500 rows
    . . imported "SH"."SUPPLEMENTARY_DEMOGRAPHICS" 695.9 KB 4500 rows
    . . imported "OE"."PRODUCT_DESCRIPTIONS" 2.379 MB 8640 rows
    . . imported "SH"."SALES":"SALES_Q4_2001" 2.257 MB 69749 rows
    . . imported "SH"."SALES":"SALES_Q1_1999" 2.070 MB 64186 rows
    . . imported "SH"."SALES":"SALES_Q3_2001" 2.129 MB 65769 rows
    . . imported "SH"."SALES":"SALES_Q1_2000" 2.011 MB 62197 rows
    . . imported "SH"."SALES":"SALES_Q1_2001" 1.964 MB 60608 rows
    . . imported "SH"."SALES":"SALES_Q2_2001" 2.050 MB 63292 rows
    . . imported "SH"."SALES":"SALES_Q3_1999" 2.166 MB 67138 rows
    Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."REGIONS" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."REGIONS" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."COUNTRIES" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."COUNTRIES" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."LOCATIONS" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."LOCATIONS" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."DEPARTMENTS" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."DEPARTMENTS" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."JOBS" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."JOBS" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."EMPLOYEES" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."EMPLOYEES" TO "EXAM_03"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'USER1' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."JOB_HISTORY" TO "USER1"
    ORA-39083: Object type OBJECT_GRANT failed to create with error:
    ORA-01917: user or role 'EXAM_03' does not exist
    Failing sql is:
    GRANT SELECT ON "HR"."JOB_HISTORY" TO "EXAM_03"
    ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type OBJECT_GRANT:"OE" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
    ORA-39112: Dependent object type INDEX:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type INDEX:"OE"."CUST_LNAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type INDEX:"OE"."CUST_EMAIL_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type INDEX:"PM"."PRINTMEDIA_PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_CREDIT_LIMIT_MAX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMER_ID_MIN" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"OE"."CUSTOMERS_PK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"PM"."PRINTMEDIA__PK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    ORA-39112: Dependent object type CONSTRAINT:"IX"."SYS_C005192" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUSTOMERS_PK" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_ACCOUNT_MANAGER_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_LNAME_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_EMAIL_IX" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"PM"."PRINTMEDIA_PK" creation failed
    Processing object type TABLE_EXPORT/TABLE/COMMENT
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
    ORA-39112: Dependent object type REF_CONSTRAINT:"OE"."CUSTOMERS_ACCOUNT_MANAGER_FK" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39083: Object type REF_CONSTRAINT failed to create with error:
    ORA-00942: table or view does not exist
    Failing sql is:
    ALTER TABLE "OE"."ORDERS" ADD CONSTRAINT "ORDERS_CUSTOMER_ID_FK" FOREIGN KEY ("CUSTOMER_ID") REFERENCES "OE"."CUSTOMERS" ("CUSTOMER_ID") ON DELETE SET NULL ENABLE
    ORA-39112: Dependent object type REF_CONSTRAINT:"PM"."PRINTMEDIA_FK" skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    Processing object type TABLE_EXPORT/TABLE/TRIGGER
    ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
    ORA-39082: Object type TRIGGER:"HR"."SECURE_EMPLOYEES" created with compilation warnings
    ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
    ORA-39082: Object type TRIGGER:"HR"."UPDATE_JOB_HISTORY" created with compilation warnings
    Processing object type TABLE_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
    ORA-39112: Dependent object type INDEX:"OE"."CUST_UPPER_NAME_IX" skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"OE"."CUST_UPPER_NAME_IX" creation failed
    Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"OE"."CUSTOMERS" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"PM"."PRINT_MEDIA" creation failed
    ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
    Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCACT_INSTANCE
    ORA-39112: Dependent object type PROCACT_INSTANCE skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39083: Object type PROCACT_INSTANCE failed to create with error:
    ORA-01403: no data found
    ORA-01403: no data found
    Failing sql is:
    BEGIN
    SYS.DBMS_AQ_IMP_INTERNAL.IMPORT_SIGNATURE_TABLE('AQ$_ORDERS_QUEUETABLE_G');COMMIT; END;
    Processing object type TABLE_EXPORT/TABLE/POST_INSTANCE/PROCDEPOBJ
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_V" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_N" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE_R" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."AQ$_ORDERS_QUEUETABLE_E" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    ORA-39112: Dependent object type PROCDEPOBJ:"IX"."ORDERS_QUEUE" skipped, base object type TABLE:"IX"."ORDERS_QUEUETABLE" creation failed
    Job "SYSTEM"."SYS_IMPORT_TABLESPACE_01" completed with 63 error(s) at 18:09:14

    Short of trying to then reverse-engineer the objects that are in the dump file (I believe Data Pump export files contain some XML representations of DDL in addition to various binary bits, making it potentially possible to try to scan the dump file for the object definitions), I would tend to assume that the export didn't include those type definitions.
    Since it looks like you're trying to set up the sample schemas, is there a reason that you wouldn't just run the sample schema setup scripts on the destination database? Why are you using Data Pump in the first place?
    Justin

  • Difference between ECC 6.0 and earlier versions

    Hi,
    one of the difference between ECC 6.0 and earlier versions is that instead 'WS_UPLOAD'  and 'WS_DOWNLOAD' in ECC we should use 'GUI_UPLOAD' and 'GUI_DOWNLOAD'  respectively.
    (of course SPDD and SPRO tcodes is known by everone i suppose)
    Similarly can u all put down some differences here, atleast one entry by each, I think we can make a good docu. I have searched the net for the differences but could not get much, so by each of us contributing one each, it would become good docu..for all of us.
    Thanx in advance

    Unicode Errors Encountered and their Solutions
    E1. In u201CTEXT MODEu201D the u201CENCODINGu201D addition must be specified.
         Error:
         OPEN DATASET FILE FOR OUTPUT IN TEXT MODE.
         Solution:
         OPEN DATASET FILE FOR OUTPUT IN LEGACY TEXT MODE.
    E2. In Unicode, DESCRIBE DISTANCE can only be used with the IN BYTE MODE  or  IN
          CHARACTER MODE  addition.
         Error:
         DESCRIBE DISTANCE  BETWEEN T_KOMK AND T_KOMK-HIEBO01 INTO BPOS.
         Solution:
    DESCRIBE DISTANCE  BETWEEN T_KOMK AND T_KOMK-HIENR01 INTO BPOS
    IN CHARACTER MODE.
    E3. u201CUSR02-UFLAGu201D must be a byte-type field (Typ X or XSTRING )
         Error:
         IF USR02-UFLAG O YULOCK.
         Solution:  Since the data type of USR02-UFLAG is type INT and is compared with data type
                    X u2013 Hence the error. So we  define a new variable ZULOCK and assign the
                    value of USR02-UFLAG to ZULOCK.
                  New variable             
                  DATA: ZULOCK(1) TYPE X.   "APBRP00
                  Assign value               
                                ZULOCK = USR02-UFLAG.
            Compare -
                   IF ZULOCK = YULOCK.   u201Creplace IF USR02-UFLAG O YULOCK.
    E4.  HT cannot be converted to a Character type field
    Error :
    WRITE ht TO t_data+10(2).
    Solution : Since the data type of ht is a type u2018Xu2019 and the data is been transfer to
             t_data which has a data type u2018Cu2019. value of one data type cannot be copy to
             another data type where one of them is type string .Hence the error occur,
             so the data type of ht is been change to Type u2018Cu2019
         OR
               A Tab ( value 09 ) is introduced as part of the row. The value 09 is not converted in Unicode environment. Instead we need to use class
         Error:
              DATA: BEGIN OF ht,
                   x(1) TYPE x VALUE '09',
              END OF ht.
         Solution:
                  Define Class after the Tables definition.
                       CLASS cl_abap_char_utilities DEFINITION LOAD.
                  Data Defination :  Comment internal table HT and define a variable HT type C.
           *   Insert + APRIA00 05/02/2007 Unicode project
           *   DATA: BEGIN OF ht,
         *         x(1) TYPE x VALUE '09'
           *   END OF ht.
         *   Insert - APRIA00 05/02/2007 Unicode project
           DATA HT type C.
           Before using HT assign Horizontal tab.
                     Ht = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.  
    E5.  In Unicode programs the u201C#u201D cannot appear in names, as it is does here in the name    u201C#LINESu201D
         Error :
         #LINES                 TYPE I,
         Solution : Since the # is used in the start of name, it is not allowed. We need to
                  remove it. 
         Solution for the above
         V_LINES                 TYPE I,
    E6. In u201CTEXT MODEu201D the u201CENCODINGu201D addition must be specified as well as the addition was required FOR OUTPUT,FOR INPUT, FOR APPENDING OR FOR UPDATE was expected.
         Error:
         OPEN DATASET PATH_NAME IN TEXT MODE.
         Solution:
         Download =     OPEN DATASET PATH_NAME FOR OUTPUT IN LEGACY TEXT MODE.
         Upload        =  OPEN DATASET AUSZUG-FILE IN TEXT MODE FOR INPUT ENCODING DEFAULT.
    E7. u201CTABu201D must be a character-type data object( data type C,N, D, T or String). Field string)    
         Error:
                data: begin of tab,                   "Excel Parameter Split at TAB
            t type x value '09',          "Tabulator
           end of tab.
                concatenate 'Material' 'Package Status'
                    into z_download-line separated by tab.
                ( In the above command  the two field are to be separated with a horizontal Tab. The earlier      way of assigning the tab value u201809u2019 will not work in Unicode environment.
         Solution:
         Define a  class just after the Table defination.
              CLASS cl_abap_char_utilities DEFINITION LOAD.
                Define  variable Tab as shown below :
              Data : TAB           TYPE C.
         Before the concatenate statement assign the value of Tab using pre-defined attributes.
              TAB = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
    E8. Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not Unicode-
          enabled; use the class cl_gui_frontend_services     
         Error-1:  Function WS_DOWNLOAD is obsolete in Unicode environment.
                call function 'WS_DOWNLOAD'
                     exporting
                          filename = zfilename
                     tables
                          data_tab = z_download.
         Solutions-1: Instead of WS_DOWNLOAD use  GUI_DOWNLOAD.
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
    *   BIN_FILESIZE                  =
        FILENAME                      = zfilename
      TABLES
        DATA_TAB                      = z_download.
    E9.  The "/" character is reserved for identification of namespaces. It must be entered twice.
            The name  of a namespace must be at least 3 characters long.
         Error :      
                     U/N(3)        TYPE C,  "U/N    --> ERSETZT DURCH SPACE
         Solution :
         * Special character can not be used to define a data variable
         *      U/N(3)        TYPE C,  "U/N    --> ERSETZT DURCH SPACE
                  U_N(3)        TYPE C,  "U/N    --> ERSETZT DURCH SPACE
         * Insert - APSUS02 07/02/2007 Unicode Project
    E10.  "LP_TAB" and "CS_TAB" are not mutually convertible. In Unicode programs,
             "LP_TAB" must have the same structure layout as "CS_TAB", independent of the length
             of a Unicode character.
         Error : This error is encountered when data from one internal table is copied to another
                             internal table which different structure. In this case its LP_TAB & CS_TAB.
                     LP_TAB[] = CS_TAB[].
         Solution :
              * Replace + APSUS02 07/02/2007  Unicode Project
    *   LP_TAB[] = CS_TAB[].
                  move-corresponding CS_TAB to LP_TAB.
              * Replace + APSUS02 07/02/2007  Unicode Project
    E11.  Could not specify the access range automatically. This means that you need a RANGE
              addition.          
         Error :  Range need to be specified as an addition to the command.
                DO 4 TIMES VARYING HELP_CHAR FROM ABCD(1) NEXT ABCD+1(1).
               Solution : 
                DO 4 TIMES VARYING HELP_CHAR FROM ABCD(1) NEXT ABCD+1(1)
              * Insert + APSUS02 07/02/2007  Unicode Project.
                                                          RANGE ABCD+0(4).
    * Insert - APSUS02 07/02/2007  Unicode Project.
    E12 .  Processing Terminated Error code: Error in opening /
                                              Path not found when downloading to Unix directory.
         Error : PARAMETER: outfile(92) DEFAULT
                  '/CP/interface/NPP/data/MX/cbslaprcpts'
                        LOWER CASE,
                   kmxmstrd AS CHECKBOX.
                This error is encountered when the path is missing. The above path is related to CCP.
         Solution:  For testing purpose comment the original path and replace it with
                                     /CP/interface/CCD/Unicode_test/ 
    E13.    Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not                                                                       Unicode- enabled; use the class cl_gui_frontend_services
         Error: Function WS_UPLOAD is obsolete in Unicode environment. (During UCCHECK)
                   Call function 'WS_UPLOAD'
           Exporting
                Filename                = zfilename
                Filetype                = u2018DATu2019
           Tables
                data_tab                = z_upload
           Exceptions
                Conversion_error        = 1
                file_open_error         = 2
                file_read_error         = 3
                invalid_table_width     = 4
                invalid_type            = 5
                no_batch                = 6
                unknown_error           = 7
                gui_refuse_filetransfer = 8
                others                  = 9.
         Solution: Instead of WS_UPLOAD use TEXT_CONVERT_XLS_TO_SAP. Do not use temporary file put the file name as it is.
    1) First define a type pool and a variable of type truxs_t_text_data.
    TYPE-POOLS: truxs.
    DATA: it_raw TYPE truxs_t_text_data.
         2) Use this it_raw in the function module in parameter i_tab_raw_data. Put file name and the internal table in the function module.
    CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
        EXPORTING
    *     I_FIELD_SEPERATOR        =
    *      i_line_header            =  ' '
          i_tab_raw_data           =  it_raw       " WORK TABLE
          i_filename               =  zfilename
        TABLES
          i_tab_converted_data     = z_upload[]    "ACTUAL DATA
       EXCEPTIONS
          conversion_failed        = 1
          OTHERS                   = 2.
         Comment u201Ci_line headeru201D. It takes the first/ header line of the file which is to be uploaded.
    Put  square brackets after internal table as shown above.
    E14.    CURSORHOLD may not be converted into a number.
         Error:  GET CURSOR LINE CURSORHOLD VALUE CURSOR_HOLD.
         Solution: In the declaration part of CURSORHOLD, one field is of u2018Pu2019 type and one field is of u2018Iu2019 type, which is not allowed in Unicode environment.So change the the type of it to NUMC.  

  • Differences between XI 3.0 and 7.0?

    Can anyone say the difference between SAP XI 3.0 and SAP XI 7.0? Also I would like to know when 7.0 is released in the market?

    Hi,
    that's the answer I received from OSS support regarding availability of XI 7.0 (status end of last year):
    <i>the actual Release is XI 3.0 which is part of NetWeaver '04 as you
    probably now.
    XI 4.0 to XI 6.0 will be left out to synchronize the Release numbers of
    NetWeaver components.
    That means that the release which followes XI 3.0 is called XI 7.0 (and
    not XI 4.0).
    For XI point of view there is not much difference between XI 3.0 and XI
    7.0
    Regarding your question:
    unfortunately we plan to give out the next major release just about end
    of next year (2006).</i>
    regards,
    Peter

  • Difference between XI 3.0 and XI 7.0

    What is the Difference between XI 3.0 and XI 7.0?
    ( functionality & architecture wise)

    Hi,
    There is no new features added in PI7.0, if u have working on XI 3.0, PI7.0 Older versions the features same..
    But PI7.1 there is new changes u can find below.....
    Integarte SAP & Non-SAP Legacy system
    PI 7.1 is based on open, web service enabled standards and
    Integrate all SAP and non-SAP, A2A, B2B, BPM, service enabling and BAM
    Highlight of enhancement in PI7.1
    1) Enterprise Service repository (ESR) contains the design Registry
    2) Includes significant high-volume message processing is supported by message processed in a single
    Service call
    3) Also importantly support for asynchronous messaging based Reliable Messaging (WS-RM) for both
    Brokered communication between two systems will be supported in this release.
    4) Provide Service Registry benefits based on UDDI 3.0
    Enterprise Service Repository
    In PI7.1 ES Repository is at the heart of Enterprise SOA
    ES Repository is really the master data repository of service objects for Enterprise SOA
    It contains the definition & process of services
    In ES Repository has two parts, one is the ES Repository and the other being the Services Registry
    ES Repository (ESR) is really the master data repository of service objects for Enterprise SOA
    Besides service definition the ES Repository also provides you with a central point for finding and
    Managing service metadata from different sources, including application deployments - this is
    Where the Services Registry comes in. The Services Registry is the UDDI part of the ESR which
    Enables service consumers to find services
    The SAP XI Integration Repository used by process integration has become the basis of the central Enterprise Service Repository: powering Enterprise SOA and Service Enablement.
    Objects in the ES Repository include:
    Global Data Types (CCTS based)
    Process Component Models
    Executable Integration Processes (BPEL)
    Integration Scenarios
    Service Interfaces (Enterprise Services)
    Interface Mappings
    Enterprise Services built in the ES Repository
    Enterprise Services includes:
    Are built using a consistent enterprise model based on: GDTs, Process Components, and Business Objects.
    Are based on open standards.
    Are mapped to the Service Interface object in the ES Repository.
    Global Data Types - Building blocks for Service Interfaces
    Defined in the ES Repository
    Defined company-wide based on open standards (ISO 15000-5, UN/CEFACT CCTS)
    Reusable semantic building blocks for service interfaces and message types
    Process Component Models
    Drill down from high-level models to service interfaces and operations
    Process component architecture models enable SOA governance
    Process components expose on enterprise services, which are based on service operations
    Web Services Reliable Messaging (WS-RM)
    Asynchronous messaging (EO, EOIO) based on open WS standard
    Support Business Activity Monitoring (BAM)
    Embedded Event Infrastructure: Collecting, pre-filtering and publication of events across SAP and non-SAP systems.
    Event handling: cast the local event to an event proxy to send out event messages to event Consumers.
    Transaction SWF_BAM for event filtering via filter rules and event handling.
    Enhancement for Mapping
    Re-usable user defined functions.
    Look-up function reads multiple fields.
    Synchronous DB RFC lookups: Use graphical function to model look-ups.
    Specify mapping parameters at configuration time.
    Principle Propagation based on SAML
    This feature uses the WS-RM protocol.
    The implementation of this feature is based on the open standard SAML and can
    be used with backend systems that support the SAML technology.
    Forward user context from sender to receiver.
    Authorization check in receiving system based on original user.
    Support BAM Milestone Modeling (BPEL)
    Sub-Process Calls: Integration Process Call,
    User Interaction: User Decisions (initially not part of this project, but will be covered as well to draw the complete picture),
    Alert Categories
    Enhancements for Process Automation
    Human interaction:
    Integration paradigm (design/ configuration).
    Generic user decision.
    Language dependent texts for end-user display, enriched with variables.
    WS-BPEL 2.0 adoption: Preview and implementation BPEL4People, BPEL-SPE Simple user defined functions can be configured directly in the process.
    reward points if helpful...
    PrasHanT

  • Difference between scom 2012 sp1 and SCOM 2012 R2

    what is the difference between scom 2012 sp1 and SCOM 2012 R2 ?

    What's New in System Center 2012 R2 Operations Manager:
    https://technet.microsoft.com/en-us/library/dn249700.aspx

  • Difference between J1IEX Part 1 and J1IEX Part 2 in local excise invoice

    Dear all
    difference between J1IEX Part 1 and J1IEX Part 2 in local excise invoice or local po
    regard
    nabil

    >
    sayednabil wrote:
    > Dear all
    >
    > difference between J1IEX Part 1 and J1IEX Part 2 in local excise invoice or local po
    >
    > regard
    > nabil
    Hi Syed,
    J1iex Part1 is the term referred to with the Part1 registers in Indian Excise scenario.
    There are basically two type of Part1 registers RG23A-1 & RG23C-I based on material type A(raw material) or C(Capital Goods)
    Part1 register contains only the material quantity & unit of measure.
    Similarly The J1IEX Part2 is referred to RG23 Part2 registers which are again RG23A-2 & RG23C-2 based on material types.
    Part2 registers are containing only Excise duty part which has been taken credit.
    hope it assists...

  • Differences between BC Set SOLMAN40_CHARM_BASICFUNC_001 and database.

    Hello Team,
    We are configuring Change Request management in Solution manager.
    Activation of BC sets ends with warning.Activation log shows below error.
    'Differences between BC Set SOLMAN40_CHARM_BASICFUNC_001 and database. Check values'
    There errors like "
    Field Not Copied
    Difference between BC Set and Table"
    We are through with note :903527  which suggest "2) Create a new transport request (Transaction SE09) in the source client of your Solution Manager system. Unpack the file Piecelist_Change_Management_Init.zip, which is attached to this note. Copy the contents of the file Piecelist_Change_Management_Initial.txt into the transport request. Use Transaction SCC1 to import the transport request into your Solution Manager client"
    But how to "Copy the contents of the file Piecelist_Change_Management_Initial.txt into the transport request"?
    Please let me know if you have any hint.
    Best Regards,
    Tushar

    status/action??
    when u click action tab in maintenance transaction the status updated auomatically.
    have u checked the errors shown in error tab....after u removed the errors....
    thn u choose up 'update maintenance cycle' action press save button the status will be same but error button wiil be green
    Then u have action Next phase"'in dev with release"
    If it is not appearing even there is no error........Pls  ck the action profile or ask solman consultant to chk the same
    Hope it clarifies
    Regards
    Prakhar

  • What is the difference between PO Charge Account and PO Accrue Account ?

    Hi
    On Requistion's Distribution screen , there is a A/c codes exists : PO Charge , Accrue, Budget & Variance .
    Can anyone explain me the exact purpose of the same and what is the difference between PO Charge Account and PO Accrue Account ?
    regards
    Thanks
    SD

    Hi Sanjay,
    Here is the OA help (11i) :
    Entering Purchase Order Distributions:
    6. Enter the purchasing accounts. When you save your changes in this window, Purchasing uses the Account Generator to automatically create the following accounts for each distribution:
    Charge: the account to charge for the cost of this item in the purchasing operating unit
    Accrual: the AP accrual account in the purchasing operating unit
    Variance: the invoice price variance account in the purchasing operating unit
    Destination Charge: the account to charge for the cost of this item in the destination operating unit
    Destination Variance: the invoice price variance account in the destination operating unit
    Note: The last two accounts are created only if the receiving destination operating unit is different than the purchasing operating unit and there is a transaction flow defined between the two organizations.
    If you are using encumbrance control, Purchasing also creates the following account for each distribution:
    Budget: the encumbrance budget account
    The Account Generator creates these accounts based on predefined rules. See: Using the Account Generator in Oracle Purchasing.Hope it helps
    Xavier

  • What is the difference between JSR 168 portlets and WSRP portlets?

    What is the difference between JSR 168 portlets and WSRP portlets?

    Here is the difference between JSR168 and WSRP:
    The WSRP specification does not make any statements as to implemention. Java's portlet specification, JSR 168, and WSRP are not competing technologies. JSR 168 may be used to define a portlet, and WSRP may be used to define a portlet's operations to remote containers. JSR 168 portlets and WSRP may be used together to define a portlet and to provide remote operations. Similarly, .NET portlets may be created for use with WSRP. Interoperability between JSR 168 and .NET WSRP implementations has been demonstrated

  • Difference between Security Oracle user and Security User

    Hi All,
    Can anyone give me the difference between Security-> Oracle -> user and Security-> User in System Administrator Resp of oracle apps R12.
    Thanks,
    Mahesh.
    Edited by: 991854 on Mar 12, 2013 1:49 AM

    Can anyone give me the difference between Security-> Oracle -> user and Security-> User in System Administrator Resp of oracle apps R12.Security > Oracle > Register:
    Use this window to register an ORACLE username with Oracle E-Business Suite. An ORACLE username grants access privileges to the ORACLE database
    http://docs.oracle.com/cd/E18727_01/doc.121/e12893/T174296T174305.htm
    Security > Oracle > Data Group:
    A data group defines the mapping between Oracle E-Business Suite products and ORACLE database IDs. A data group determines which Oracle database accounts a responsibility's forms, concurrent programs, and reports connect to. See: Defining Data Groups, Oracle E-Business Suite System Administrator's Guide - Configuration.
    http://docs.oracle.com/cd/E18727_01/doc.121/e12843/T156458T156461.htm
    Security > User > Define:
    Use this window to define an Oracle E-Business Suite user. This user is an authorized user of Oracle E-Business Suite, and is uniquely identified by a username.
    http://docs.oracle.com/cd/E18727_01/doc.121/e12843/T156458T156461.htm
    Thanks,
    Hussein

  • Difference between system level privilege and object level privilege

    hi
    i just want to know the difference between system level privileges and object level privilege.
    please correct me if i am wrong
    with system level privilege user can create objects such as creating tables,view,synonyms etc
    where as in object privilege we can only manipulate operations on object i.e perform dml not ddl
    please help

    Hi,
    810345 wrote:
    hi
    i just want to know the difference between system level privileges and object level privilege.
    please correct me if i am wrong
    with system level privilege user can create objects such as creating tables,view,synonyms etc
    where as in object privilege we can only manipulate operations on object i.e perform dml not ddl There are some system privileges that only concern manipulating objects: SELECT ANY TABLE, for example.
    The main difference is that the system-level privileges tend to cover all objects of a certain type, including objects that haven't been created yet.
    Object-level privileges usually apply only to one specifi object, such as one particular table, and are lost if the object is dropped. (For example, if I create a table called table_x, give you SELECT pivileges on it, then you can query my table. But if I then drop table_x and re-create it, you will not be able to see it unless I grant the privilege again.)

Maybe you are looking for