Difference between Order Header BSD and operation schedule SSD

Hi,
One of your Client is operating on SAP 4.7
There are some cases where Order Header Basic Start Date and operation Schedule Date are no same.
example:
Present Order Basic Start Date 24.06.2011
Present Order Basic Finish Date 01.07.2011
Forward Schedled order.
Operation 1
Operation 2
Work Center has sufficient capacity and is available to perform work 24hrs.
Using planning board CM10 user dispatches operation 1 to 30.06.2011 and operation 2 to 01.07.2011.
The problem is order basic start date is remaining same i.e. 24.06.2011 and not chaning to 30.06.2011.
Can any one please help in this issue.

yes for all order types and also i have observed that most of work order has basic start date as 24.06.2011 when all the operations of orders are scheduled in future dates (date other than 24.06.2011).
The first time scheduling of work order operation is done on 24.06.2011 (CM10) and then after re-scheduling (through IW38) of operation changed the schedule start date but work ordre basic start date remained same i.e 24.06.2011.
Dispite of first time scheduling and then re-scheduling basic start date remained 24.06.2011.
Note: Same profile was selected in both CM10 and IW38 while accessing planning board.

Similar Messages

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 "Order to Delivery" and "Order to Cash"

Hi,
This could be a basic question. But, can any one tell me the difference between 'Order to Delivery" and "Order to Cash" Process.
Thanks
Anitha

hi
Order to cash cycle in SD starts with Inquiry -> Quotation -> Order -> Delivery ->Picking-->Post Goods Issue -> Invoice -> Accounting Document generation
For Inquiry
Doc. Type: IN
T.Code: VA11(create), VA12(change), VA13(display)
Process: Quotation
Doc. Type: QT
T.Code: VA21(create), VA22(change), VA23(display)
Process: Order
T.Code: VA01(create), VA02(change), VA03(display)
Doc. Type: OR
For Delivery
Doc. Type: LF
T.Code: VL01N(create), VL02N(change), VL03(display)
For Billing
Doc. Type: F2
T.Code: VF01(cre ate), VF02(change), VF03(display)
For Accounting Document
T.Code: FB03(display)
where as ORDER TO DELIVERY
Delivery Order is the term of core team normally used for Delivery. Ideally insome of the legacy, they do not create Sales Order & use the term Delivery Order for Delivery.
InSAP, we mornally map it as Sales order --> Delivery --> Post Goods issue --> Billing.
At times we have to give meaning to the term sprecified by core team / end user & arrive at SAP terminology.

Cost difference between PM report MCI8 and IW38 orders cost

Hi Experts!
I have an issue of cost difference between Plant Maintenance total actual cost of orders and Cost analysis report.
Short Text
Cost difference between PM report MCI8 and IW38 orders cost
Long Text
Applied SAP notes 180047 and 112841 for the following error:
Cost is not displaying in MCI8 for every 3 months intervals.
Now this problem has been resolved but got an another error like cost
difference between MCI8 report and IW38 order costs.
Note applied method:-
1). Configured FYV as Z1 with Period update for info structures S61 to
S65, S70, S114 to S116.
2). Regenerate order cost in Tcode OLI5.
3). PMIS: Statistical setup of info structures T.Code u2013 OLPM
For Info Structures which is changed in the configuration SO61-SO65,
SO70, S114-S116.
4). Copy info structures Version &( to Active version 000 T.Code u2013 OLIX,
Select Copy version
For all info Structure SO61-SO65, SO70, S114-S116.
*Steps for Reconstruction*
New another error like cost difference between MCI8 report and IW38
order costs.
Step 1. Transaction- MCI8, Order type - CORR, Period -01.2009 to
12.2009 and execute
Step 2. Drilldown the corrective maintenance order costs into period
wise.
Step 3. Transaction- IW38, Order type Corr, Period -01.2009 to 12.2009,
Currency - EUR and execute
Cost differences: E.g. Example A)
                               MCI8                                 IW38
Total costs             8.041,69                           5.544,99
of WOs               18                                     18
So far my view is that, regardless of the selection criteria or the
output layout, predominantly the costs are different.
I would expect that they are equal. And what the right result are,..u2026Iu2019m
not sure.
Regards,
Santhamoorthy

Hello,
Sometimes this difference comes because of the selection period which we are choosing.
Try to run IW38 once with the help of Basic start and basic finish dates of the order.
And after that with the help of the period with the same dates range.
You will get the difference also.
the reason is that whenever any Posting is done in the previous month PM order the system changes the basic start date and when you select the current period and execute IW38 it shows the whole cost incurred on the order including all previous cost.
But in MCI8 it does not happen because MCI8 is run through LIS structures. And in this report only the current month cost will be shown by the system.
I hope you got the idea about differences.
Regards
Naveen

Difference between ordered by and sorted by?

hi,
Can any1 tell me wats the actual difference between ordered by and sorted by???

Generally speaking, when talking math, one talks about an "ordering" in some set of values. Usually one doesn't actually place them in order; the order is already there, implicit in the values. When talking computer science, one talks about "sorting" because the values may be in a sequence which violates the desired order, and you have to sort the sequence to match the order. "Sorting" isn't as relevant in math because there is no sense of the items being out of sequence when the order is established.
So "order" describes the ideal (which mathematicians care about).
"Sort" describes the practical, the activity needed to make the real match the ideal (which computer sciences care about).
That's my intuitive feeling on it, anyway.

Difference between SAP 4.7 and ECC 5.0

hi frnds
.what is the difference between SAP 4.7 and ECC 5.0?
regards

Hi,
Following are the basic differences as far as MM Module is concerned
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
Goods receipt
Goods issue
Transfer posting
Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
107: Goods receipt to valuated goods receipt blocked stock
109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location
Regards
Priyanka.P
AWARD IF HELPFULL

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

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

Difference between ISA 5.0 and ISA 7.0

Dear ISA gurus,
Can you please tell me what is the difference between ISA 5.0 and 7.0. Are there any changes in the ISA architechture. Is there any change in ISA Java API. Appreciate your pointers here.
Thanks!
Surya.

Hi
The ISA/ E-Commerce architecture remains the same , however we do have some functional enhancements.
Enhancements in SAP CRM 2007
1. The Web Catalog Management application has been replaced by the
Catalog Management work centerthat is available with the WebChannel Manager role in SAP CRM
The programming interface SAPTREX API replaces the SRET APIinterface that was used in SAP
CRM 5.0
2. New business process Sales Order Processing B2C for Service Providers in
CRM Web Channel. This process covers:Selling of packages, rate plans,
incentives, and enabling productsCollecting technical data Automatic contract creation for rate plan items
prices)
Management
3.Dynamic field control for orders Search for items in orders,quotations, and order templates.
4. Enhancements of the B2C Webshop UI: Catalog navigation, Webshop header, mini shopping basket,
shopping basket, scale price display Verification word for integration with Interaction Center
5. Additional way to display products in product catalog via block view
Paging through list of (special and personalized) offers on Web shop home page
Display of number of pages in catalog area browsing.
Warm Regards,
Sumit

Difference between Invoice created date and billing date.

Hi Gurus,
I opened the Billing Document in display mode(T.Code:VF03).In header data I found two tabs one is Created On and another one is Billing Date. Here in the billing document the both dates were different.
Please let me know the difference between Created On date and Billing Date.
your afforts are highly appriciated.
JYothi.

Dear Jyothisd,
Invoice created date : Invoice created date is nothing but the date on which you have created the invoice.
Billingdate:Billing date is the date on which you suppose to do the billing for respective customer. Tease billing dates will be proposed to invoice from sales order if it is order related or else actual goods issue date is proposed to billing document as a Billing date if particular billing document is delivery related.
If you want you can change the Actual billing date the result is invoice created date.
Please revert if you want any further clarifications
Thanks&Regards

Difference between BSI 8.0 and 8.0G

Hello All
Can someone tell me the Difference between BSI 8.0 and 8.0G?
Thanks

Charlene :
Below is the cut and paste message from BSI on the reason of BSI 80g to be used on first payroll on 2008. In short, this version contains certain critical tax change/calculation not in lower version of BSI 80 (e.g. e and f). If you already upgraded to BSI 80, then this is just a cyclic update (not as bad as from 70 to 80) plus tubs up to 68 (to include PA tax changes).
Rgds.
Please note this is a Mandatory cyclic upgrade, due to BSI modifications to benefit plan and earning type data layout information, and to accommodate additional Pennsylvania Local Services Tax (LST) changes effective January 1, 2008. Pennsylvania Local Services Tax (LST) rates are scheduled to be published by the Department of Community and Economic Development (DCED) on December 15, 2007. BSI will issue the pertinent data updates shortly thereafter. Due to the anticipated volume of changes, we expect to issue the data updates over several TUBs.
This cyclic upgrade must be installed as soon as possible, prior to running your first 2008 payroll, in order to keep your TaxFactory system current. Please check with your vendor for certification information.

Exact Difference between Non Stock NLAG and Non Valuated UNBW Materia type

Dear All
What is the Exact Difference between Non Stock NLAG and Non Valuated UNBW Materia type?
I tried creating Purchase Order and found that accouting doc got created at both times and stock was not updated in MMBE for both material types.
Regards

Hi,
non-valuated material (Material Type UNBW):
This type of material is managed on a quantity basis, but not on a value basis. This makes sense for materials of low value, stocks of which nevertheless have to be monitored (for example, operating manuals).
Non-stock material (NLAG) (Material Type NLAG):
Inventory management is not possible for these materials either on a quantity or value basis. For frequently required consumables, the use of this material type nevertheless enables you to store the information required to create
purchasing documents (such as texts and units of measure).
When a material is procured directly for consumption, no material master record is necessary. In connection with consumable materials, you can distinguish between the following cases:
Consumable material without material master record
Consumable material with material master record that is not subject to
inventory management (on either a quantity or value basis)
Consumable material with material master record that is subject to inventory management on a quantity, but not a value, basis
Regards,
Pardeep malik

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'z the difference between the Commercial Invoices and

What'z the difference between the Commercial Invoices and
Invoices/Excise Invoices? Also I understand that we can combine 2~3
invoices and can create one commercial invoice? If it is possible, how
to create the same?
cheers
shalsa007....

Hello,
A commercial invoice is a bill for the goods from the seller to the buyer. Commercial invoices are utilized by customs officials to determine the value of the goods in order to assess customs duties and taxes.
In general there is no standard form for a commercial invoice although they tend to contain many of the following features:
     seller's contact information
     buyer's contact information
     consignee's contact information (if it is different from the buyers)
     invoice date
     a unique invoice number
     sales terms (usually in incoterm format)
     payment terms
     currency of sale
     full quantities and description of merchandise (Generally this includes unit price and total price. Product descriptions should be consistent with the buyer's purchase order. Including the Harmonized System commodity codes can be helpful, especially in countries that are WTO members.)
Excise invoice Original for Buyer copy, whether prices are inclusive or exclusive of excise duty.
The invoice in which the Excise duties are included.
As per Indian tax system, Excise duty (16%) is payable by each manufacturing unit on the value of manufactured goods / on the value added. The manufacturing plant is supposed to submit an excise duty report on fortnightly / monthly basis. Various registers (RG1, RG23A, RG23C, PLA) are maintained for that purpose, which record all the transactions including movement of goods, cenvat credit available and cash balance available.
In SAP, we use transaction j1id for configuration and j1iin, j2i7, j1i5, j2i5, j2i6, j1ip for creating, extracting and printing excise invoice.
*Please reward if this helps**
Regards
AK

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.

Difference between Order Header BSD and operation schedule SSD

Similar Messages

Maybe you are looking for