Beruflich Dokumente
Kultur Dokumente
InfoSource
Demand Planning Week (Future) 8YGTDS_C30 0EMPLOYEE
Customers: Item(0FI_AR_3)
Customers: Item(0FI_AR_3) 2LIS_11_VASCL ( Sales Order Schedule Line (As of 2.0B) ) 1_CO_PA0011
8YGTDSO03
GT_MV_TGT2 - Yesterday
0WBS_ELEMT_ATTR_Delta 0WBS_ELEMT ( Work breakdown structure element (WBS element) 2LIS_05_QVUDN_DELTA_QM_Usage _Decision_01 2LIS_05_UDN ( Inspection Lots with Usage Decision )
2LIS_03_BF - Delta IM Movements 2LIS_11_VASCL YGTDS_GTDP_PLAD12 ( DP Day from Planning Area D12 ) 2LIS_11_VAITM ( Sales Order Item Data (As of 2.0B) ) 2LIS_12_VCITM ( Delivery Item Data (As of 2.0B) ) 2LIS_12_VCSCL ( Sales-Shipping: Schedule Line Delivery (As o
2LIS_12_VCITM_DELTA 2LIS_12_VCSCL_DELTA
YGT_MV_ACT - Full
1_CO_PA0011 Delta
1_CO_PA0011
2LIS_11_VASCL_DELTA
YGTGD033
8YGTDSO40
Error
Process overdue Error when writing in PSA
Error message from the source system Error when reading from the qRFC queue: QSTATE = WAITUPDA RSQU 31'.
Error message from the source system Error when reading from the qRFC queue: QSTATE = WAITUPDA RSQU 31'. Value 0001CL100000000000 not contained in the master data table for YSHIPTO_S Processing is overdue
Transaction Data Failure due to unauthorized characters in Master Data YQUANS Value '!S?0X<40 ' (Hex ' ') of char. 0BATCH contains unauthorized characters
Delta update not possible until after initialization of the delta process Error occurred when reading SID for InfoObject '0INSP_LOT ' with value '040000008500 '
No SID found for value '000010012801 ' of characteristic 0COORDER IPG doesn't start Action was cancelled Error occurred in the source system Data Source must be replicated
Error occurred in the source system/Error 7 when sending an Idocs/ Time limit exceeded
Error when writing data into ODS: DB_TABLE_SET_LOCK-1Error when generating the update program/ An error occurred in the program generation for InfoSource 1_CO_PA0011 and InfoCube/ODS table YGTFCPA01 . This may be extrapolated to incorrect update rules.
"Request REQU_3PM0HXUHXP8Y8YKSUDAQRD3Q(107.399) has not or not correctly been updated: Please edit"
Resolution
1. Delete request from Data Target YGTDS_C31 2. Manually update failed data packet
Document link
Error 2 Error 3
1. Delete content of ODS YGTGD004, Cube ZANGDFIAR. 2. Manually turn red to delta or delta init extract to red. 3. Delete entry in the initialization option for source system via menu item Scheduler 4. Step 3 should delete entry 0FI_AR_3 in tcode RSA7 and tcode SMQ1(BW1020FI_AR_3)in R/3'. 5. If step 4 does not happen, delete manually in R/3 via RSA7 and SMQ1 6. Delete all PSA of 0FI_AR_3 INIT and Delta loads. 7. Reinitialize delta in BW.
Error 6
To avoid delta initialization, OSS note 444261 option 4 is applied Refer to the email next column 1. Delete record from the PSA 2. Reprocess the request Manual update the failed data packets
OSS444261
Error 9 Error 10
New fix
1. Delete record from the PSA 2. Reprocess the request 1. Delete record from the PSA 2. Reprocess the request
Error 9
Proc 17
1. Open the system 2. Activate the Infocube YGTDS_C03 3. Create a transport request (In description type: Do not transport) 4. Manually force to red 5. Delete the bad request from Data target 6. Reran IP 7. If failed and we cannot fix it, open a ticket and exclude IP from IPG 8. If success, delete the transport request. /SE10 8. Don't forget to close the system 1. Search the object YGTTPVAR in Data target 2. Deleted bad request from Data target 3. Reran IP 1. Go to monitor 2. Chose detail tab 3. Search the red packets 4. Right click on it and manual update 1. Search the InfoSources and select the Infopackage with "INIT" in the name 2. Select Scheduler -> Initialization options for source system from the menu bar 3. Select the init entry and delete it 4. Select Yes on the prompts 5. Run the INIT InfoPackage Try to fix it with the procedure in the link or open a ticket for functional team 1.Search the Infoobject 0COORDER 2. Activate Master Data 3. Delete bad request from Data Target YGTDSO40 4. Read everything in manually
Error 19
Error 11 Error 12
Reran request 1. Replicate Data Source 2. Activate transfer rules for the InfoSource
Error 13
Error 15
Error 16
Load first to PSA then to data targets, with a master data consistency check turned on
Force the QM status for day the info package ran to red and subsequently delete the request from all cubes. This allowed us to continue pushing psa requests to the ODS 1. Delete failed request from all datatargets 2. Force read the failed request. 3. Run IP 'YGTMBATCH_ATTR - adhoc' with Batch number = 33350078 on select data tab. It takes 2 minutes and only extract records where batch number is 33350078. 4. Repeat delta IP 'Delta package for update by ODS YGTDSO4'.
Error 17 Error 18
Option I
Procedure name
How to postpone daily data load How to Open and Close the system How to handle failed IP that cannot fixed and is neccesary open a ticket How to reload a failed hierarchy infopackage How to reprocess a failed request ( First method) How to reprocess a failed request (Second method) How to reprocess a failed request ( Third method) How to activate transfer rules for an InfoSource How to resolve "No access permission as table is already locked" How to create a ticket for Master Data issue How to exclude an infopackage from IPG How to force QM status to turn into red How to fix a Transaction Data Load Failure How to run an initial load when a delta has failed How to delete a bad request from infocube with aggregates How to change the owner of a job in BW How to delete from PSA How to delete a record in the request in PSA How to delete requests from PSA How to activate and fill aggregates in a quick way How to push data from PSA to ODS
How to automate the aggreates and activate aggregates for COPA PAC01 How to fix problem when info doesn't appear in /OYBW03 Report Roll up process after BC02 aggregates activation Delete bad request from data target and reran request How to populate YBW03 report How to initialize ODS 46 and 33 What to do when Change Run fail of MD table lock What to do when Change Run fail because of the rollups How to stop/start the Transaction Data to run
How to run Apply Hierarchy/ Attribute Change out side of the event chain. How to get the record number / packet in a PSA
How to check master data YGTMBATCH How to run BW nightly dataload report Create SID for 0SalesEmply BW Schedule linkages (Predecesors and succesors events) List of IP's with error messages that can be forced to green with markets approval Duplicate records in YGTTPPP03 (IPG GTTP_Transaction_Data_Daily1 run multiple times) \How to fix duplicated issue for YGTTPVAR
Document link
Proc 1 Proc 2 Proc 3 Proc 4 Proc 5 Proc 18 Proc 6 Proc 7 Proc 8 Proc 9 Proc 10 Proc 11 Proc 12 Proc 13 Proc 14 Proc 15 Proc 16 Proc 17 Proc 18 Proc 19 Proc 20 Proc 21 Proc 22 Proc 23 Proc 24 Proc 25 Proc 26 Proc 27 Proc27 Proc28 Proc29 Proc 30 Proc 31 Proc 32 Proc 33 Proc 34 List Proc 35 Proc 36
OpenDate
Ticket No.
System
Infopackage
Error
12/21/2003
IM0826646
AA4
Value 0001CL100000000000 not contained in the master data table 2LIS_11_VASCL_DELTA for YSHIPTO_S
12/11/2003 RM0805448
AA4
YGTGD_DERIVE_NS C_EXCEPTION FULL Taking long time for loading the data in AA4
Error occurred in the source system Error when reading from the qRFC queue: QSTATE = WAITUPDA
7/24/2003
IM0424604
AA4
6/14/2003 IM0340338
AA4
YGTGD_DERIVE_NSC_ Update terminated because InfoPackage contains duplicate data EXCEPTION - FULL/ records
6/14/2003
IM0341093
AA4
6/14/2003 IM0340345
AA4
Field YYWWNCH will not be delivered from DataSource YGTGD_CUSTGROUP_SALESCHANNEL in source system YGTGD_CUSTGROUP_ AA2PRRC102. SALESCHANNEL - FULL
7/21/2003
IM0418376
AA4
7/19/2003
IM0414886
A04
YGTGD_YTERRITORY_ HIER YGTGD_YTERRITORY_HIER-A04 C35 PreProd BW extraction error due to authorization failure Error in source system: C35PPRH402 Message: User RFC-BIWA04 has no RFC authorization for function group RSAK .
7/14/2003
IM0401726
A04
40 + IP failures
7/11/2003
RM0395493
A04
Error occurred when reading SID for InfoObject '0VOLUMEUNIT ' with value 'ZB2 '
7/5/2003 7/5/2003
IM0383895 IM0383880
A04 AA4
Error occurred when reading SID for InfoObject '0INSP_LOT ' with 2LIS_05_QVUDN_DELT value A_QM '010000013087 ' YGTDS_0APO_PPDS_O PERATION_01 PPDS dataload has failed with the follwoing error message .IP:
The following DSP weekly dataload has failed today and all of them has failed with same error . I dont see any system issue on the AA3 side . Invalid data status /SAPAPO/TSM 219 Errors in source system RSM 340 7/6/2003 IM0384394 AA4 DSP Weekly IPG 0CUST_SALES_LKDH_ HIER (YCUSTHIER) See log: Incorrect hierarchy structure in the consistency check Node ID 00049015 does not exist, Node ID 00098627 does not exist.
6/27/2003 IM0367309
AA4
6/11/2003
IM0333899
AA4
GTDS_0APO_PPDS_OP Error occurred when reading SID for InfoObject '0APO_LPROD ' ERATION_01 - Full Load with value ' 000000000000000000000000000000'
Error occurred in the source system Error when reading from the qRFC queue: QSTATE = WAITUPDA 6/25/2003 IM0365150 AA4 0FI_AR_3 (Delta load) 0CUST_SALES_LKDH_ HIER (YCUSTHIER) See log: Incorrect hierarchy structure in the consistency check Node ID 00049015 does not exist, Node ID 00098554 does not exist.
6/25/2003
IM0362851
AA4
6/4/2003
IM0322671
A04
0CRM_SALES_ORDER_ I - INIT No SID found for value 'LET ' of characteristic 0CRM_ACTCAT YGTGD_CUSTGROUP_ SALESCHANNEL - FULL Transfer structure is not yet active
6/5/2003
IM0324136
A04
6/4/2003
IM0321413
AA4
YGTGD_YACTDOCU FULL
Value 'No ' (Hex ' ') of char. YQUANS contains unauthorized characters
6/11/2003
IM0334211
A04
0CRM_SALES_ACT_1 DELTA
6/16/2003
IM0343605
AA4
Production dataload problem, Transaction data did not load. 0CRM_MKTELM1_ATTR - FULL 0CRM_MKTELM2_ATTR - FULL 0CRM_MKTELM5_ATTR - FULL No SID found for value '003 ' of characteristic 0CRM_PRIO 2LIS_05_QVUDN_DELT A_QM_Usage_Decision_ Error occurred when reading SID for InfoObject '0INSP_LOT ' with 01 value '040000008500 '
6/10/2003
IM0331340
AA4
6/23/2003 11/8/2003
IM0356939 IM0711465
A04
AA4
A04
A04
Short dump in AA2, Function module "/BI0/QI0FI_AR_30002" not found. Syntax error in GP$ERR$PSTRU_PAREA_EXTRACT_ , row YGTDS_PLAW30_MA 142 (-> long text) Errors in source system LO
YGTHR_0EMPLOYEE_A TTR
Assign to
Status
Opened
Close date
AMS_SAP GD
Opened
OV
12/17/2003
GCC_ISIT BW ADM
CB
GCC_SAP BIW
GCC_ISIT BW ADM
GCC_SAP BIW
MARCELO. MARDONE S
7/23/2003
CL
7/23/2003
Closed
CB
7/15/2003
AMS_SAP_T&P
Closed
AMS_SAP T&P
Closed
BW BW
7/8/2003 Closed
BW
AMS_SAP GD
Closed
CB
CB
GCC_ISIT BW ADM
Resolved
CB
AMS_SAP GD
Closed
CB
6/26/2003
Closed
MA
6/12/2003
Closed
OV
6/13/2003
Closed
OV
6/9/2003
AMS_SAP_GD
Closed
CB
6/13/2003
GCC-BW-ADMIN
Closed
CB
6/16/2003
Closed
CB
6/22/2003
Closed
OV CL
6/25/2003
12/3/2003
MA CL
12/4/2003
Last update
This issue has occurred before in BW Prod and an initial load was required taking over 12 hours. SAP needs to look at this error in the system as we have tried in the past to have them access the system in a timely manner to replicate this error without success. A High Priority message should be opened with SAP to look at the problem in AA4 and AA2.
Fixpack 9 is beiing applied in R11 (development landscape). on Wednesday of this week. We anticipate that this will move through the landscape one week per environment so that testing across the project can be completed. This should resolve this error. we will see with a greater degree of certainty in Regression and Pre-production. Thanks Craig Date of Activity: 06/16/03 08:32:28 Operator: VANESSA.SARRO@NESTLE.COM Activity Type: Reassignment Description of the Activity Performed: Reassignment from GCC_ISIT BW ADM to CSC_SERVICEDESK Cynthia, I killed all the deltas, and previous INIt and the error message that "there is an error in last delta...can not be updated.." continuous appearing. I'm investiganting this issue. Best Regards This infopackage will no longer be needed when the Sales Credit derivation is in the system. 07/23/03 08:31:51 (CYNTHIA.LEE@US.NESTLE.COM): BW DP weekly run was not triggered due to some authorization problem. The job which triggers the event to start the weekly run was created by user 'DEFERNA' whose access to AA4 has been taken away. The whole IPG has been rerun successfully. Thanks, Cynthia Technical error 23/07/03 16:11:22 (ALEXANDRE.FATOBENE@BR.NESTLE.COM): It was a Test done by the LGO. CGN2153 Please ignore the Error. The Market was adsived to delete the Territory in MSY Technical error There was a refresh on C35. No accesswas possible to C35 between this operation. Presently the refresh is done : you could run the extraction job. Hi Olga, This is because the uoM 'NL' hasn't been copied from R/3 to BW. (ZB2 is what's held in the database, NL is what the user sees). Missing loads run on next day of ticket creation and any additional actions were required. Missing loads have been loaded into data target. Data loads have been checked in the cube "YGTTPQM11" and it contains data in relation to the missing Inspection Lot master data information in BW. Therefore this ticket will be closed. - (Liloff Ramos) 7/7/2003
From: Cooper,Nicholas Elliott,VEVEY,GL-GT Sent: Tuesday,1. July 2003 10:34 To: Vollet,Rodolfo,SAO PAULO,GLOBE Center AMS Cc: Lee,Cynthia,GLENDALE,GLOBE Center AMS Subject: RE: Incident IM0333899 has been assigned to your group
Hi Rodolfo, It seems the problem record has disappeared from the data load. This is because either: 1) the data has been fixed in PP/DS 2) the time criteria in the infopackage means it is not loaded. I managed to successfully load the operation infopackage today. My advice is to get rid of all the old data and reload, just to make sure the data is up to date: 1) delete all the contents of YGTDSO03, YGTDS_C63, YGTDS_C03 2) re-run the infopackages: YGTDS_0APO_PPDS_OPERATION_01 - Full Load YGTDS_0APO_PPDS_RESCAPREQ_01 - Full Load PS - the loads to the archive cube should have been turned off with a manual action of RFC8556, but looking at Ulrich's CID it wasn't fully clear. I'll send a new CID through to fix this. Nick Reason not listed here.
Hi all, The reinitialization of 0FI_AR_3 was performed on Sunday successfully. Today the delta was loaded to PSA with success. Hi AMS BW admins, Are you going to update the datatargets from PSA? I will close the Peregrine and OSS because there is no way to reproduce the error again. Our suggestions are the following: 1) As soon as the error occurs again please be ready to create userid and to open the connection for SAP. 2) Let us ask an outage for the investigation period. Thanks, Slava.. 26/06/03 10:48:28 (MARCELO.BERNARDELLI@BR.NESTLE.COM): The problem was solved as you can see in attached file (upload.doc). Thank you.
Date of Activity: 06/12/03 23:57:43 Operator: SHERI.FARR@NESTLE.COM Activity Type: Assignment Description of the Activity Performed: Individual reassignment from NONE to KEVIN.CALLINSWOOD@NESTLE.COM assign
Ticket has been solved, as per last data load. There aren't any additional action to be done in relation to it. Liloff Reason not listed here
Ticket opened. Sent email to Slava to emphasis criticallity of the report. SAP message has been created OSS 0120050410 539
Status Date
Closed
26-Feb AA4
N/A
Closed
27-Feb AA4
0CRM_SALES_ORDER_I - DELTA
Closed Closed
N/A N/A
YGTFCPA03, YGTFCPA01 & YGTFCCSES cubes Delta package for update by ODS YGTGD017 Init. package for update by ODS YGTGD046 Init. package for update by ODS YGTGD033
Closed
28-Feb AA4
BW CI 20738
YGTFCPA03 Delta package for update by ODS YGTGD017 YGTFCPLA_adhoc IPG FICO Material Ledger 2004 Adhoc
Pending
3-Mar AA4
0CRM_SALES_ORDER_I
RM01010540
YGTFCPLA YGTGDBC02
Closed
10-Mar A04
2LIS_01_S680_DELTA
Closed Closed
N/A N/A
0CO_PC_02_0011_PERIODEND_CLOSING n/a
Closed
23-Mar AA4
8YGTTPPP03 - Delta
Open Closed
Closed
22-Apr AA4
1_CO_PA0011 Delta
Closed
22-Apr AA4
NA
Closed
22-Apr AA4
NA
0CUST_SALES_LKDH_HIER
Closed
22-Apr AA4
NA
Closed
1-May AA4
IM1205704
2LIS_11_VAITM_DELTA
Open
1-May AA4
YGTGDMC01
Open Open
YGTDS_M05 YGTDS_M07
Closed
1-May AA3
GTDP_Transaction_Data_Daily
Issue / Error
Error: No valid master data for YGTMBATCH 000000000011261811 40550076CM (With Different batches)
0CRM_SALES_ORDER_I - INIT ran successfully on feb 18 and delta on feb 23 but taking very long time
Filling aggregates running for these cubes Still running/ failed with process overdue
Update date for YGTGDMC01 not current though the data targets are updated correctly. Dataload schedule again Extraction process takes long time (2.5 hrs)
Delta update not possible until after initialization of the delta process
Company Code CL10, Plant 0107 Failed with master data issue, Douglas working on it. Company Code CL10, Plant 0076 is in progress. All other ones are completed for Material Ledger. Once previous is complete, we can start working with the second excel document that Douglas included in his email. Aggregates/Fillups running Transaction Data load in progress Request REQU_3SSQ2V75K804ZS6RHK3K3EZA5 (253.505 ) has not or not correctly been update
No valid assignment from SalesOrg/Division/DistibutionChan/Customer CL10/00/04/0000020562 to Channel level 1 S YGTGD017 Please inform elisa rodrigues that the LIS 02, LIS03, & LIS05 initializations were successful. Ask her if there is anything else we need to do from our end..
Processing overdue There is an monthly HR report which is n/a in AA4. It last ran on 2/1. The IP appears to be a datamart, but I didn't feel comfortable executing withoutCynthia's advise 8YGTTPPP03 - Delta failed with error "Delta upload is only possible after successful initialization". Requested Cynthia to enquire about next steps
Init ran on 19th by Cynthia but since then the IP is still not included in the daily run. Any reason? Loads being re-constructed for data targets YGTFCPA03 and YGTFCPA01
Error message from the source system Error when reading from the qRFC queue: QSTATE = WAITUPDA
Processing overdue
Running
FiscaL YEAR VARIANT NC IS NOT MAINTAINED FOR CALENDAR YEAR 4004 YGTGDMC01 is used for Critical reports. Wanted to check the status of the request that are available for today. System giving an error: "Cube is not a basis info cube. Administration not available" YGTDS_M05 is used for Non Critical reports. Wanted to check the status of the request that are available for today. System giving an error: "Cube is not a basis info cube. Administration not available" YGTDS_M07 does not exist in the data targets but is referenced in daily status report APO Job did not run though event chain GTDP-DATALOAD-CHAINGD1 is properly registered. No valid assignment from SalesOrg/Division/DistibutionChan/Customer CL10/00/04/0000020562 to Channel level 1. No valid assignment from SalesOrg/Division/DistibutionChan/Customer CL10/00/04/0000020562 to Channel level 2 No valid assignment from SalesOrg/Division/DistibutionChan/Customer CL10/00/04/0000020562 to Channel level 3 Aggregates/Fillups running Processing overdue, Caller 70 missing
BW Admin notes
Resoltuion notes
Changed IP to load all batch #'s.. It was mistakenly loading only one
e.g. load started.. Please monitor I saw that last delta ran successfully but took 2 days 10 hrs to complete on feb 23 for 82007 records and the ticket was resolved by Nick Cooper on feb 24. Currently this IP is descheduled, can we include again this IP for daily load even if this is taking long time to complete? Please advise. The aggregate fill for YGTFCPA01 & YGTFCCSES cubes are done. For YGTFCPA03 got cancelled after the job failed with system exception. Inorder to speed up the aggregate fills, statitics is run on PA03. Please restart the fills for PA03 after COPA nightly delta load. Deleted request from cube YGTGD17 and forced to red delta
Delta is still running well over 24hrs.. As a result, the nightly load fails because the load from the previous day is still running.. We've unscheduled the IP from the DL and have sent an e-mail to the BASL's to see if we can schedule this IP on a weekly basis
Job finished, however problems persisted.. Cynthia to restructure aggregates ran ok on 29 Feb load
CI completed
Please monitor Still Running. Please monitor. 2 Still Running. Please monitor. Once previous IP's finish, please start this IPG and monitor Please run this after the previous run completes
Job finished, however problems persisted.. Cynthia to restructure aggregates Reran request.. Loaded successfully Load completed successfully IPG started IP has been descheduled. E-mail sent to the BASL's in an attempt to have this IP loaded on a weekly basis
Can we force the one for plant 0107 to green? This is in green in the cubes but red in the monitor, I have not deleted the requests yet. For plant 076 is still running, please Waiting feedback from Douglas Cotrim monitor. for the one that failed. Please monitor Completed Please monitor. Daily Status Check list is up to date. Cynthia working in initialization for this IP I deschedule this delta Forced it to green with error No valid assignment from SalesOrg/Division/DistibutionChan/Custo mer CL10/00/04/0000020562 to Channel level 1 Load failed. Reran successfully
Please monitor
The IP was triggered by Olga and failed. Load failed on 16 and 17 with the same The failed requested was deleted and IP error though IP ran succesfully on 18th rerun March. IP is disabled for daily load. IP descheduled
CI 22916 is not implemented fully in AA4, therefore dleta is excluded. Please followup with Cynthia Reinitialization required next R/3 outage Please monitor This completed successfully Forced it to green with error No valid assignment from SalesOrg/Division/DistibutionChan/Custo mer CL10/00/04/0000020562 to Channel level 1 We have two fixes in our knowledge base in the errors section, I think the better one is the one in the record number 5, but I didn't want to change the I just deleted bad request from ODS value from the nosend=U is changed to YGTGD004 and forced delta to red. nosend=X in the table TRFCQOUT, I Please help to fix it. was not sure about it. Scheduled for Daily Run. This IP failed after 3 hrs running, IPG GTDP_Master_Data_Daily1 however job Job IP was deschedule and we will have to BI_HIER3TIR9KPBUECH4WJLADK4M0 manually execute this one at 5pm X06 is still active. System time. Ticket Opened - RS
Please monitor The problem is in MDR, as BTC said we need delete some nodes is Customer Hierarchy in MDR, after that load Customer Hierarchy to R3 and at the end load to BW.
Ran it amnually and next day onwards this got triggered automatically - not an issue any more
Forced to green with error. Please watch Has failed the previous 2 days and has been running for 3 hours