SOBJ current setting (oss note 135028, 77430)
Hi all,
I'm working in a ECC6 R/3 system.
In according with sap notes 135028 and 77430 I would modify standard current setting for some views used in customizing transaction.
Reading note 135028 I follow the indicated solution :
"...open the IMG and display the IMG structure. Position the cursor
on the corresponding IMG activity and select the menu path "Edit -> Display
IMG activity". On the following screen, select the Tab "Maint.objects". A
list of the assigned Customizing objects is displayed. By double-clicking
on the corresponding row, navigate to the Customizing object and set the
Indicator "Current settings" directly......."
At this point the system requires to entry a key for standard object modification.
Is it allowed from sap to modify this kind of object?
My boss asked me to show him a script from sap where it's clear that it's a normal activity to change a standard object in this cases.
Can anyone help me?
Thanks in advance.
S.M.
OB52 need not be made available to users. There are alternative transactions in SAP Easy Access to achieve the same functionality ready-to-use.
One such txn is S_ALR_87003642.
Try it, and if it suits your purpose ask your BASIS team to give users access to this txn. That should do it.
If you are in the mood to explore, another (a little more sophisticated) option is S_PEN_05000130.
Thanks
Gulshan
Similar Messages
-
I'm currently signed onto my home network and want to go on with another computer but don't remember my password for my network. Does anyone know where to find this? It's a password that I set myself, not the one that came with my router.
It's in your Keychain on the computer you usually use to connect to your network - the "kind" will be "AirPort Network Password".
Your Keychain can be opened by using the Keychain Access program. It is in your Utilities Folder.
Open Keychain Access, and type airport in the search field. You will see a number of entries. Choose the one with the name of your wireless network, open it, and check the box next to "show password". Before it reveals itself you will be asked for your login password - the one you use to log in to your MacBook.
The network password will appear in the box.
Quit Keychain Access. -
I can't open some photoshop files it says "The command "Set" is not currently available."
What does this mean and how can I fix it? A corworker will make a photoshop file (Poster for example) and when i try to open it on my computer it wont open and says "The command “Set” is not currently available." What does this mean and how can I fix it? Thanks!
You are running some sort of automation when you open files - because that error message comes from automation (actions, scripts or plugins) that are trying to target something that isn't there.
Event Scripts was the obvious choice.
Automation plugins, or Flash Panels are the next most obvious -- try disabling all third party plugins and Flash Panels.
The error might come from Generator, if you have the latest Photoshop CC. -
OSS notes for BSI TUBS replace W4 setting in T5UTZ for CO with a 3
Every time we import and apply the OSS notes associated with BSI TUBs that include table T5UTZ, it replaces the value indicating W4 availability with a value of '3' which does not allow a records specialist to enter Infotype 0210 for Colorado. We have no information that this is no longer required. Can anyone point me to why this setting is indicating that the CO W4 information will default to the Federal record every time the table is delivered in an OSS note.
Any help would be greatly appreciated.
Thanks
JohnHi Raj,
select the lines which you want to delete then click on Dlete button. and click on insert to insert the lines.
if you use them then the comments will be generated automatically some thing like this
for deletion..
*{deleted
for insert
*{inserted
insert and delete buttons are next to Modification over view button.
Regards
vijay
Message was edited by: Vijay Babu Dudla -
My iphone 4 is not working when i insert the sim message is showing that the iphone is not currently set up to work with carrier or request that this iphone be unlocked? what i have to do.. help please?
To use a sim from a carrier, other than the carrier your phone is locked to, requires that your phone be officially unlocked. The only way to accomplish that is to contact the carrier your phone is currently locked to & request that they authorize the phone's official unlocking.
-
OSS note 1044741 contains no correction instructions for 46C.
I am trying to apply OSS note 1044741 to fix BC Set creation for deleted table entries. However OSS note 1044741 contains no correction instructions for 46C. Please provide assistance.
Bruce ReevesDear Bruce,
How to raise an OSS note:
In service.sap.com, choose Keys and Requests -> Development Requests -> Create Development Request
The Create development request form appears. It is divided into the sections described below:
Classification
In the 'Classification' section of the form, you can classify your request by selecting various criteria from the listboxes. This information is used for reporting purposes and to assign your request to a processor at SAP.
Reporting unit is only displayed for information. It defines if you enter the request for yourself, on behalf of a Customer Competence Center (CCC), of a customer, or of a user group. Which entries are available depends on the organization you are working for.
Priority defines the priority this request has for you.
Industry is only displayed for information. This is the industry of your company.
Other Industry allows you to select further industries if the request refers not only to your industry. To select more than one industry, hold down the <Ctrl> key and select the desired items by clicking on them.
Component defines the application component to which your request applies.
Core release defines the R/3 release you are currently working with.
Add-on defines, in case the request applies to an industry solution, the specific add-on release you are currently working with.
General provides generic features for a better classification of your request. If you wish to define more than one category, hold down the <Ctrl> key and select the desired items by clicking on them.
Cross-component provides cross-component features for a better classification of your request. If you wish to define more than one application, hold down the <Ctrl> key and select the desired items by clicking on them.
Only relevant for country allows you to specify that your request is only relevant for the selected country.
Personal classification by requestor
In the 'Personal classification by requestor' section, you can add your own classification criteria to the request:
Classification 1 - 3: allows you to specify your own features, e.g., "Project xyz". You can enter any text up to 30 characters in these fields.
Description
In the Description section of the form, you can describe in detail the feature you request for the SAP software.
In the Language field, select the language in which you are describing your request. For processing at SAP, all non-English requests will be translated into English.
In the Short text field, enter a meaningful title for your request.
The Long text field is mandatory. Use it to describe your request in detail. Even if you attach external description files, please enter a detailed description here.
The Business need field is mandatory. Please use it to explain why the requested feature is needed for your business.
The Example field is collapsed by default. Click on the plus symbol to the left of the field to expand the entry field, and enter an example for the requested feature.
The Current workaround field is collapsed by default. Click on the plus symbol to the left of the field to expand the entry field, and describe which procedure you currently use instead of the requested feature.
The Proposed solution field is collapsed by default. Click on the plus symbol to the left of the field to expand the entry field, and describe how you propose to solve the issue related to your request.
Attaching documents
You can also attach files that further describe your request, for example, documents or presentations. All file types supported by this site can be attached, this includes all popular Office formats.
To be able to attach files to your request, you must have the Check In Wizard program installed on your computer. Otherwise, an error message will be displayed. If you do not have the Check In Wizard installed, click here to start the installation
NOTE:
This will automatically save your request with the status New. The request will, however, not yet be sent to SAP. If you have not yet filled in all required fields, the system will prompt you to do so before you can add an attachment. The attachments will be listed only after you have saved or sent the request.
To attach a file, choose Add attachment.
The Check in Files dialog box appears.
Select the file you want to attach, and choose Open.
A status dialog box appears. When the status The check in process has completed successfully is displayed, confirm with OK.
The file is now attached to the development request.
Repeat the above steps for any additional files, if required.
Saving the development request
When you have entered all required data you can save your request. To do this, choose Save. You can then edit the request and send it to SAP later. This allows a company or user group to internally manage, discuss and consolidate its development requests before it decides which development requests will be sent to SAP in the next step. (Development requests that are no longer relevant can be set to status Closed by author).
Sending the development request to SAP
When you have entered all required data, you can alternatively send the request to SAP immediately. To do this, choose Sent to SAP. You need a special authorization to use this function. If you had saved a request before but not yet sent it to SAP, you can send it to SAP later using this function.
Resetting the request form
If you make a mistake during data entry and want to reset all entries to the values they had when you opened the form, choose the Reset button.
Closing the request
If you find that you no longer need the request, you can close it. In this way, you specify that no further processing of the request is necessary.
To close the request, choose Closed by author.
(After closing, confirm the request to remove it from your inbox.)
Confirming the request
Confirm the request if you have received SAP's final decision. The development request will no longer be shown in your Inbox.
To confirm the request, choose Confirm.
You will find the answers in your SAP inbox.
Visit the following link for information regarding SAP Notes:
http://help.sap.com/saphelp_nw04/helpdata/en/b8/3cf839fd35384de10000000a11402f/frameset.htm
Hope this will help.
Regards,
Naveen. -
can anyone send me the OSS note: 99422
thanks
[email protected]Summary
Symptom
The 'Euro' currency has a separate symbol, similar to $.
Where and how can it be used?
Other terms
Character, character set, code page, currency, currency symbol, euro,
RSCP0028, RSCP0008
Reason and Prerequisites
A new character did not previously exist.
Solution
This character was invented. It looks like an epsilon with a double line or like a 'C' which is overtyped with '='.
Where and how can it be used?
Unicode
The character was imported as U+20AC with Unicode 2.1. In theory, Unicode systems should not have any problems processing these characters.
ISO 8859-15
Euro is supported in ISO8859-15. ISO8859-15 is not supported by SAP.
Microsoft
Microsoft includes the character in its code pages and fonts. Details under http://www.eu.microsoft.com/typography/faq/faq12.htm
Printer and so on
See Note 129581.
R/3 R/3 ABAP lists
Output is not possible with current system code pages for non-Unicode-systems.
Document R/3 SAPscript
See Note 129581.
Importance
In the R/3 environment the new character is classified as not very important. SAP R/3 usually uses the ISO abbreviations that consist of three "normal" letters for all currencies.
Thanks and Regards,
Vishwa.
"Saying THANKS In SDN is Thru Assigning Points ". -
How to realize current setting for TCODE FQ_FPCJ_NC?
Hi all,
does anybody knows how to change transaction FQ_FPCJ_NC into a current setting? FQ_FPCJ_NC is used in PSCD for assigning a clerk to a specific cash desk (transaction FPCJ). Although it is part of the standard area menu S000, it opens a transport after an entry / a change was made, that means every change has to be transported and every new assigned clerk has first to be created in the developing system. I cannot find neither any maintainance object for transaction SOBJ nor any customizing activity.
Does anybody has a helping idea?
Regards,
FrankHi Kevin,
Yeah I read the thread earlier too and it was helpul to some extent.
I used CALLBACK routines to get the data and then passed the old and new structures to BUP_MEMORY_BUT000_FILL to populate the data.
But even then that field is not getting set.
Is there something else that i need to do after passing changed structure to BUP_MEMORY_BUT000_FILL?
I posted on that thread too but didn't get any reply from Paul
'BUPA_GENERAL_CALLBACK returns the tables LT_BUT000_OLD n new. Both contain the values of BUT000 that are present on BP before my changes are saved.
Regards,
Shaili
Edited by: shailip on Aug 25, 2009 11:37 AM
Edited by: shailip on Aug 25, 2009 11:38 AM
Edited by: shailip on Aug 25, 2009 11:39 AM -
Can anybody send me the oss notes 322526.
Summary
Symptom
Workflow is not working as you expect.
Other terms
workflow, BBP, Business to Business Procurement, CRM, SWUD, OOCU, SWEL, SWI1, SWO1, PFTC, SWUS, SWUE, event, event log,
Reason and Prerequisites
This note contains transactions and techniques that will help you
understand and analyze your workflow problems.
Transaction SWUD
SWUD is the diagnosis transaction. This will guide you through the fault finding process. The check-list order is determined dynamically according to:
a) your workflow definition and
b) the statistics of the most common mistakes made when creating/activating a workflow.
The testbed, provides a launchpad for tests to ensure that your workflow definition is rugged enough for the production environment. It also allows you to access the tasks, subflows, object types, delegated object types and agent assignments directly, without going through the workflow builder first. (Foreground tasks with no agent assignment are marked in red from release 4.5 onwards). This list is also useful as a catalogue of the components of workflow for documentation or transport purposes.
Click on the "info" icon to read a description of the test being performed.
Any workflow accessed through this transaction is added to the last-used list. The workflow can be recalled at a later date by clicking on the reuse icon in the left-hand column of the last-used list.
The next section describes the transactions called from SWUD. Experts may find it easier calling them directly.
Secondary Diagnosis Transactions
Transaction SWU3: Verify Workflow Customizing.
In this transaction the most important basic customizing for workflow is checked. If you find any errors here, read the documentation for the error. If your system is BBP or CRM, see note 60801.
Transaction SWEL: Event Log.
Note: Before you can use the event log, you must make sure it is activated. You check this in transaction SWELS. If you are not sure whether or not it is active, just deactivate and activate the event log once.
WARNING: An activated event log can lead to bad performance, and must not be activated constantly in a productive system.
Transaction SWE2: Event type linkage
A workflow is usually started or triggered by an EVENT so it is important to make sure that an event occurrs. In the event log you can see the event and its business object type.
If an event has been successfully created, it is important to check if there is a receiver type for this event. The receiver type is the workflow that has been triggered by the event.
The coupling between an event and the receiver can be maintained in trans. SWE2.
Transaction SWU0: Event simulation
If you have found NO receiver type in the event log, then you should check transaction SWU0, Simulate Events.
In this transaction you can simulate an event. The system will check all workflows that could be triggered by the event and tells you whether or not they were triggered. Information is displayed for the workflows that were not triggered successfully.
Transaction SWI1: Work item list
If a workflow was been correctly triggered and started at least one WORK ITEM should be created. You can view the work items in transaction SWI1, Work Item Selection.
The easiest way for the selection is just to go into this transaction after you have checked the event log. By default all the work items of the last hour will be displayed.
You will find in this transaction the work item number, the status of the work item and the workflow task that has created the work item. Furthermore, (in the technical workitem display) you can have a look at the container by selecting a work item and using the menu GOTO -> CONTAINER. To display the work item details double click on the item. From the details you can see the selected/ possible/excluded agents for this work item by using the menu GOTO -> AGENT -> SELECTED/POSSIBLE/EXCLUDED AGENTS.
When the status of the work item shows an error you should have a look at the workflow log using the menu EDIT -> DISPLAY WORKFLOW LOG. Here you can see errors that have occurred.
Transaction PFTC/SWDD: Task editor/Workflow Builder
If you want to have a look at the definition of the workflow you can use transaction PFTC, Maintain Tasks.
The button WORKFLOW BUILDER brings you to a graphical display of the workflow structure which is fairly easy to read and understand. On the tabstrip TRIGGERING EVENTS you can check if the triggering is activated or not and deactivate/activate it by clicking on the icon in front of the event.
Transaction OOCU: Customizing overview
To check if the relevant tasks are activated and users are assigned, you can use transaction OOCU; Task Customizing Overview.
In this transaction all the tasks are sorted by the application components and are thus easy to find. Note that if you have almost no entries in this transaction, you should execute the report RS_APPL_REFRESH in transaction SE38.
Transaction SWUE/SWUS: Event/workflow trigger
If you have activated a user exit, e.g. for the role determination, and you have problems with that, you most probably have to debug the workflow. This can be done using the transaction SWUS or SWUE.
With SWUE you can create an event. After you entered object type and event you have to fill the event parameters and the key for a specific object. If you want to debug the workflow you have to set the flag TRIGGER RECIEVER FM SYNCHR. If you have set a break point in your user exit or in any other function module of the workflow the system will stop at this break point and you can start analyzing.
The second possibility to debug a workflow is to use the transaction SWUS, the workflow test environment. In this transaction you have to enter the workflow task and fill the input data. Please use the F4-help to fill the input data. Here again you have to set a break point in your user exit or in any other function module of the workflow and then the system will stop there.
Summary of the manual alternative to SWUD
Now that you have a better understanding of how to use these transactions, you can follow the steps below to quickly analyze your workflow problems:
1. Go to transaction SWU3 and check if everything is okay. If it is not, please fix it before you proceed.
2. Go to transaction SWEL and check if an event is created. If not, check in transaction SWELS if the event log is activated.
If you see an event but no workflow is triggered, proceed with step 3.
If you see an event and a workflow is triggered, but the status of the triggering shows an error, proceed with step 3.
If you see an event and a workflow is triggered and there is no error, proceed with step 4.
If the event log is activated and you do not get any event, open up a message using the component of the application to which the business object type belongs. From release 20C for creation of shopping carts
the architecture of workflows changed and no events are visible!
3. Go to transaction SWU0 and simulate the event. Is the workflow that you expect to be triggered visible in the simulation?
If it is not, then check the workflow definition in PFTC. The event must be defined as triggering event.
If it is, but the event linkage is not activated, go to transaction OOCU and activated it.
If it is visible, but it is not activated, go to transaction PFTC and activate it.
4. Go to transaction SWI1. Search for the work item that belongs to the workflow. Check the status of the work item.
If it shows an error, look at the workflow log. Do you see any errors? If yes, you can probably find a solution in the SAPNet Frontend. (Tips and tricks on how to search for information and solutions in the SAPNet Frontend can be found in note 192194.) If you do not find any help in the SAPNet Frontend, please open up a message with the component BC-BMT-WFM and tell us the number of the error message and the name of the workflow.
Solution
If you can not solve your issue with these hints, please open up a
message with the component of the application of the workflow (can be
seen in the transaction PFTC on the first screen). Please include the
results of the steps 1 to 4, which will help us a lot to analyze your
issue.
Header Data
Release Status: Released for Customer
Released on: 06.09.2001 22:00:00
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-BMT-WFM Business Workflow
Secondary Components: SRM-EBP-WFL Workflow
Releases
Release Independant
Related Notes
887304 - MIC:FAQ, Workflow, Email, Scheduling
856911 - SRM 5.0 Installation: Composite Note
737800 - Enhancements to upgrade on SAP CRM 4.0 SR1
396779 - Create shopping basket: Error in workflow Customizing
373675 - Problems with invoice generation (check list)
329564 - Approval status display incorrect in BBPPU02
323170 - Problems with confirmation
192194 - Tips for the note search/problem analysis
60801 - HR-OM: Error message 5A378 inconsistency SOBJ
Print Selected Notes (PDF)
Attributes
Attribute Value
weitere Komponenten 0000031067 -
Can anyone tell me where to see OSS notes
Hi
Can anyone tell me where to see composite OSS note 586163 (any OSS notes). In which site and in which category i should search.www.service.sap.com
SAP Support Portal
Quick Lnks :
Search for OSS notes.
You need to have a login..its not free.
After login - Help & Support - Search for SAP notes
<b>
Anyws here is the note</b>
Summary
Symptom
You are transferring data from SAP R/3 Inventory Management to the BW system. You get unexpected data or data that differs from the data in the analyses in the R/3 system.
This note should help you to analyze this problem.
Other terms
2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 2LIS_03_S195,
2LIS_03_S196, 2LIS_03_S197, 2LIS_03_S198, 0IC_C01, 0IC_02, 0IC_C03,
0IC_MC01, 0IC_MC02, 0IC_MC03, stock analyses, inventory management,
Non-cumulative InfoCubes, stock key figures, stock, stocks,
RMCBINIT_BW, RMCBNERP, RMCBNEUA, consistency,
data consistency, healthcare, health service
Reason and Prerequisites
This note provides an overview of the release strategy, sources of information, tips and tricks, and known errors for this subject area.
Solution
Contents
1. Release strategy
a) General information
b) Recommended objects for BW Releases 3.0B, 3.1 Content and 3.2 Content
c) Recommended objects for BW Releases 2.0B and 2.1C
d) Obsolete objects
e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
2. Sources of information
a) BW technology
SAP BW online documentation
"How to" documents
b) Business Content
Online documentation for BI Content
Extraction Documentation:
"How to" documents
Plug-In information
3. Extracting non-cumulative data from R/3
a) Explanations for the extraction
b) Known errors
Stocks (2LIS_40_S278/2LIS_03_BX)
Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
Industry-specific notes
4. Technical information regarding non-cumulative info cubes in BW
a) Warehouse Management
b) Queries
c) Update rules
d) Known errors
5. Stock Analyses in BW
a) Explanations on data flow
b) Known errors
c) Tips and tricks
6. Performance
1. Release strategy
Use the following objects depending on your BW and R/3 or plug-in releases:
a) General information
The following basic principle applies: The 0IC_C03 InfoCube (material movements) replaces the 0IC_C01 (material movement plant) and 0IC_C02 (material movements storage location) InfoCubes. The 2LIS_03_BX (material stocks) InfoSource or DataSource replaces the 2LIS_40_S278 (transfer BW: stock) 2LIS_03_S197 (material stocks storage location) and 2LIS_03_S198 (material stocks plant) InfoSource or DataSource. The 2LIS_03_BF (material movements) InfoSource or DataSource replaces the 2LIS_03_S195 (material movements storage location) and 2LIS_03_S196 (material movements plant) InfoSource or DataSource.
We therefore STRONGLY recommend that you use the OIC_C03, 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM objects. We will continue to deliver and support any other objects mentioned in this note, but only for reasons of downward compatibility. These objects will not be enhanced because they are based on obsolete technology.
For information about the general support for DataSources based on information structures, see also Note 543002.
As of PI 2002.2, the 2LIS_03_BX DataSource is available for Release 4.0B and higher.
As of PI 2001.2, the 2LIS_03_BF and 2LIS_03_UM DataSources are available for Release 4.0B and higher.
The 0IC_C03 InfoCube is available as of Release 3.0B.
b) Recommended objects for BW Release 3.0B and higher
InfoCube: 0IC_C03 (Material movements)
InfoSources and update rules:
2LIS_03_BX (stocks) - available for Release 3.0B as of Support Package 10
2LIS_03_BF (movements)
2LIS_03_UM (revaluations)
If your Support Package version for Release 3.0B is Support Package 9 or lower, you have the alternative option of using the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons stated above, we recommend that you change to 2LIS_03_BX as of Support Package 10. For more information, see Note 588015.
c) Recommended objects for BW Releases 2.0B and 2.1C
InfoSources: 2LIS_03_BX (stocks) - available for Release 2.0B as of Support Package 30
- available for Release 2.1C as ofSupport Package 22
2LIS_03_BF (movements)
2LIS_03_UM (revaluations)
If you are using Release 2.0B Support Package 29 or lower or Release 2.1C Support Package 21 or lower, you can alternatively use the 2LIS_40_S278 InfoSource or DataSource. However, for the reasons given above, we recommend that you change to 2LIS_03_BX as of Support Package 30/Support Package 22. For more information, see Note 588015. Unfortunately, we cannot provide the 0IC_C03 InfoCube and related update rules. If you need to use this InfoCube, we can provide a similar solution to the one provided for Releases 3.0B or higher as part of a consulting project. Note that Note 589024 does not apply in this case.
d) Obsolete objects
If you are using R/3 Release 3.1I and do not intend to upgrade to a higher release (regardless of the BW release) in the foreseeable future, use only the 0IC_C01 and 0IC_C02 InfoCubes and the related InfoSources or DataSources 2LIS_03_S195 - 2LIS_03_S198. If you are using the Healthcare industry solution and are interested in using the 0IC_C01_Q0020 and 0IC_C01_Q0021 queries, you can also use the 0IC_C01 InfoCube and related objects. Unfortunately, there is no automatic data migration for the transition from 0IC_C01/2 to 0IC_C03. See also Note 804781 for a complete overview of all key figures in 0IC_C03 that are also possible in 0IC_C01/2.
e) Queries/Web templates of the 0IC_01, 0IC_C02 and 0IC_C03 InfoCubes
For more information, see Note 591063.
2. Sources of information
The main sources of information are located in the BW online documentation in the BW section of the SAP Service Marketplace and in the IMG documentation for the Plug-In. Other useful information is contained in various notes. These notes are listed under headings 3 - 6 below.
a) BW technology
This area contains documentation on the technical mapping of stock analyses in SAP BW.
Online documentation SAP BW (http://help.sap.com)
-> Documentation -> SAP NetWeaver -> '04
-> Information Integration -> SAP BW
i Stocks
-> BI Platform -> OLAP
-> Performance Optimization -> Stocks
ii Validity Table
-> Data Warehousing
-> Administrator Workbench -> Modeling -> InfoCube
-> Additional functions for InfoCube maintenance
-> Stock Parameter Maintenance
iii Compression
-> Data Warehousing
-> Administrator Workbench -> Data Warehouse Management
-> Process Management
-> Managing Data Targets
-> Managing InfoCubes -> InfoCube Compression
iv Aggregation
-> Data Warehousing
-> Administrator Workbench -> Modeling
-> InfoObject -> Create InfoObject: Key Figure
-> Aggregation v Exception Aggregation
-> BI Platform -> OLAP
-> Special OLAP Functions and Services
-> Aggregation
-> Scenarios for the Use of an Exception Aggregation
"How to" documents
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> In the information index: N ("Non-cumulatives") ->
"Non-Cumulative Values 3.x (ppt)"
b) Business Content
This area contains the business content representation of stock analyses in SAP BW, based on the SAP R/3 process and object model.
Online documentation for BI Content (http://help.sap.com)
-> Documentation -> SAP NetWeaver -> '04
-> Information Integration: BI Content
-> BI Content -> Supply Chain Management
-> Supply Chain Performance Management -> Inventory Management
Documentation for extraction (OLTP system)
-> Transaction SBIW
-> Business Information Warehouse
-> Settings for application-specific DataSources
-> Logistics
Here you will find the relevant documentation for each of the relevant nodes.
"How to" documents
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: N ("Non-cumulatives") ->
"How to... Handle inventory management scenarios in SAP BW 3.x" (pdf)
Plug-In information
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW Extractors - Plug-in
3. Extracting non-cumulative data from R/3
This section explains the extraction process in the R/3 system and it gives an overview of known errors and their solutions.
a) Explanations for the extraction
Determining transaction keys
Note 492828
Determining the component
When stocks are initialized, the 'MM' core application is transferred, regardless of which component you specify in Customizing under 'Specify Industry' (TAC MCB_). You must implement Note 323018 for this purpose.
In most cases, the 'MM' Core application is also used when you initialize documents and for the delta load. However, 'IS-R' is transferred as the component if Retail is set as the component and you are working with stock transfers or movements for material group articles (MATNR <> MATBF).
To create the component, the BW enrichment is required during extraction. For more information, see Notes 315880 and 353042.
The "GETSYSDEF" report provides the system setting.
Creating non-cumulative relevance
In general, the non-cumulative relevance is set to '1', meaning 'relevant'. The exceptions are consumption postings (BSTTYP = V and BSTAUS = V) and postings for material group articles (MATNR <> MATBF). Value '2' is assigned in these cases.
Logistics data extraction: Customizing Cockpit (transaction LBWE)
You can configure the 2LIS_03_BF und 2LIS_03_UM DataSources in application 03. You cannot configure the 2LIS_03_BX DataSource in the Customizing Cockpit. To activate the 2LIS_03_BX DataSource, see Note 631345.
Generic extraction of stocks
This function is available as of PI 2003.1. For lower release levels, a consulting solution can be implemented on request (contact SAP in this case).
User exit (SAP enhancement RSAP0001)
Note 413807
Update methods/extract structures/XPRAs
i Update methods (V3 update, DeltaQueue, and so on).
Notes 380078, 396647, 486784 and 505700.
For information about the automatic conversion of update methods in the logistics extraction, refer to the release notes for plug-in 2003.1
DataSources for application 03 are delivered by default with the "Unserialized V3 Update" method.
A change to "Queued Delta" may occur.
For performance reasons, you should not select "Direct Delta".
ii Changes to extract structures/XPRAs
Notes 328181, 489259, 511657 and 566917.
If you try to add another field from the pool to the "2LIS_03_BF" DataSource , the system issues error message "D0 322".
Possible reason:
XPRA "RMCSBWXP_IM_01" did not run after you imported the plug-in. This XPRA is responsible for comparing customer fields in the extract structure (enhancement) with new default fields in the extract structure (SAP). This error message appears as a result.
b) Known errors
Stocks, movements and revaluations are transferred to BW using various extractors. All known errors and proposed solutions of these three extractors are listed below.
Stocks (2LIS_03_BX/2LIS_40_S278) -> see Note 691228.
i Rounding error/valuation at company code level
Notes 663681 and 762219
ii Project stocks
Note 535657
iii Valuated sales order stocks or project stocks
Notes 487043, 616119, 674351 and 756151
iv Vendor consignment stocks
Notes 585619 and 726485
v Special stocks for customers/vendors
Note 533682
vi Valuation class
Note 684789
vii Stock in transit
Notes 767786 and 898231
Movements and revaluations (2LIS_03_BF and 2LIS_03_UM)
i Delta ability/procedure
Notes 385703 and 581778
ii Update methods (V3 update, delta queue, qRFC and so on)
Notes 339691, 444261, 498484 and 631562
iii Missing BW derivation (component,
transaction key, and so on)
Notes 315880 and 353042
Caution: You MUST read these notes
BEFORE you transfer data to the BW system.
iv Movements (2LIS_03_BF)
- Returnable packaging with customer
Notes 512597 and 530730
- Vendor consignment
Notes 585139 and 607710
- Project stocks
Note 522770
- Stock transfers
Notes 399929, 557378 and 628090 (stock in transit/
valuation type)
- Purchase orders with account assignment (consumptions)
Notes 587320 and 629726 (non-valuated materials,
see also Notes 752607 and 790506)
- Batches
Notes 445632 and 685450
- Incorrect stock type
Notes 438649 and 451355
- Customer consignment
Note 563342
- Incorrect / missing valuation class
Notes 735425, 747581 and 770858
- Returns (movement types 122/123)
Notes 741396 and 763424
- Profit center
Note 769660
- Subsequent adjustments
Note 822396
v Revaluations (2LIS_03_UM)
- Incorrect update because the
BSTAUS and BSTTYP fields are missing
Notes 494288 and 675610
- Missing BW derivation of characteristics with settlement ofrequests
Notes 523298 and 747361
- External display of the WBS element does not exist
Note 512611
- Incorrect transaction key during setup
Note 587241
- Incorrect sign
Note 587283
- Duplicate document for MR22
Note 587304
- Incorrect/missing document number
Notes 489290, 500825, 507958, 521046, 619482,
667534, 739050, 839711, 845307, 856669 and
864630
- The BUZEI field is not filled
Note 599731
- Currency field not filled
Note 612131
- Returns (movement types 122/123)
Note 715176
- Reconstruction report RMCBNERP
Note 735209
- Missing valuation class
Note 837052
vi Master data (0STOCKTYPE/0STOCKCAT)
Note 766954
- 0STOCKCAT_TEXT is not filled since the value 'U' has not been added to the BSTTYP domain.
Note 907195
Industry-specific notes
i IS Retail
- Revaluation at retail (2LIS_40_REVAL)
Notes 533577 and 600460
- Miscellaneous
Note 841878
ii IS Oil/IS Mine
- G/L quantity for two-step stock transfer procedure
Notes 608744, 608975 and 629320
4. Technical information regarding non-cumulative info cubes in BW
In addition to the relevant sections in the online documentation, there are a number of explanatory notes that will help you to analyze problems. Section 4 e) deals with known errors and proposed solutions.
a) Warehouse Management
Validity table: Notes 360249 and 534865
Selective deletion: Note 510680
Aggregates: Note 456359
ODS capability: Notes 322303, 323811, 385099, 417703, 581778,
747037, 752492/782314 and 773823
DataMart/Open Hub capability: Notes 375098, 566145 and 566762
Compression (updating the stock marker)
->>> ESSENTIAL INFORMATION <<<-
You can see in the log whether or not the stock marker was updated during the compression (as of 3.0B Support Package 13)
For example:
"START cond CUBE IC11 at 165446 on 20030514 maxreqid 23282 maxcnsid 0 refpoint update + null elim" ->
"refpoint update" or "no refpoint update" provides the relevant information.
See Notes 613701 and 639253 if you are using Oracle 9.
Also see Notes 643687 and 655798.
For a BW system with several application servers, see also Note 834829.
->>> ESSENTIAL INFORMATION <<<-
b) Queries
-> For information about the recommended procedure for analyzing query problems see the following note: Note 370004
Slow-moving item/slow seller reports: Note 541559
A How to document is also available:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: M ("MultiProviders") -> "MultiProviders (incl. Slow Moving Item Scenario) ..."
c) Update rules
The following special features are provided for updating in non-cumulative cubes:
The non-cumulative key figure has to be included with the relevant cumulative value(s) in the InfoCube definition.
Only receipt key figures are provided for updating from the InfoSource with the stocks.
The issue and receipt key figures are provided for updating from the InfoSource with movements.
Therefore, from a technical point of view, stocks are written to the receipt key figure. The process of differentiating between the stocks and the remaining receipts then takes place in the InfoCube using record type = 1 (InfoObject: 0RECORDTP) in the technical dimension table (this also sets up the connection to the validity table).
The OLAP processor dynamically calculates non-cumulative key figures in the query (taking into account the issues/receipts and the validity table).
d) Known errors
Warehouse Management
i Loading data
Notes 534865 and 529610
ii MultiCube/MultiProvider
Note 435227
iii Compression (updating the stock markers)
Notes 613064, 613701 and 615349
iv Updating
Note 574341
Queries
i Fiscal year variant characteristic (0FISCVARNT, 0FISCPER
and 0FISCYEAR)
Note 490067
ii Exception aggregations
Notes 145630 and 607608
iii No/multiple time restrictions
Note 388983
5. Stock Analyses in BW
This section explains the data flow in BW and provides an overview of known errors and their solutions. This section also explains certain limitations and workarounds for same.
a) Explanations on data flow
See the How to paper from Section 2 b)
"How to... Handle inventory management scenarios in SAP BW 3.x" (PDF).
Note that the 2LIS_03_UM can also be loaded before the 2LIS_03_BF.
You will find further information on the SAP Service Marketplace:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW Business Content
-> SAP Supply Chain Management
-> Supply Chain Performance Management
-> In the navigation area on the left: Related Topics
-> Business Content
-> Inventory Management.
b) Known errors
0IC_C03
Notes 637927, 655798, 668085 and 710404
0IC_MC01
Note 664520
Queries
Notes 534429, 630034 and 676960
c) Tips and tricks
Analyses in BW with the storage location (0STOR_LOC) and stock characteristic (0STOCKTYPE) characteristics in the drilldown.
Solution: Note 589024 (see also Notes 201327, 322335, 456106, 506077 and 543188) and the How to document
-> http://service.sap.com/bw
-> In the navigation area on the left: Services & Implementation
-> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
"How to... Realize summarized display of stock values on storage"
Stock transfers in the two-step stock transfer procedure/differences between analyses in BW and the R/3 transaction MB5B
If you notice different results for the issue and receipt quantities of the total stock during the analysis of stock transfers in the two-step procedure, for example, storage location to storage location within a plant (movement types 351 and 101), add the "0STOCKTYPE" characteristic to the drilldown. Where necessary, filter according to the values "A" (unrestricted) and "H" (transit). You will then find the same values under stock type "A" and in transaction MB5B (if you select the storage location stock or the valuated stock).
Individual analysis of revaluations
After stock is initialized using the 2LIS_03_BX InfoSource, load revaluations into the 0IC_C03 InfoCube with the 2LIS_03_UM InfoSource. By doing this, you avoid uploading movements with the 2LIS_03_BF InfoSource. If you do so, the non-cumulative values (quantities and values) can no longer be calculated. Reason: When you initialize stocks, DIM IDs are created for 0BASE_UOM and 0LOC_CURRCY. As a result, all stock markers for 0BASE_UOM have an entry other than ' '. With revaluations, only values are updated-all quantities and their units are updated with ' '. This means that you can no longer assign revaluations to the stock markers because the units of measure are inconsistent. Solution: Update the revaluations with quantities also, as you did for the values (the result for the quantities is always RESULT = 0).
Incorrect results if quantity key figures and value key figures are analyzed together.
For example, you only displayed quantity key figures in the current drilldown. If you now add value key figures, the quantity key figures are no longer calculated correctly (the reverse also applies). As in the case of individual analyses of revaluations, movements may not be assigned to the stock markers due to missing DIM IDs. As a result, stock cannot be recalculated correctly either. This should not usually occur when the 0IC_C03 InfoCube is filled with the 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM InfoSources (this is also the case with the other relevant Business Content InfoCubes, for example 0CP_IC_C1 or 0RT_C36/37). However, it may occur because of certain loading processes, for example. Solution: Update the quantities (or values) in the same way as the values (or quantities) (RESULT = 0 is always the result for the quantities or values). See Note 643291 for the 0CP_IC_C1 InfoCube.
Enhancing the 0IC_C03 InfoCube with additional characteristics
These additional characteristics must be updated from the 2LIS_03_BX InfoSource, as well as from the 2LIS_03_BF and 2LIS_03_UM InfoSources, only then can movements be assigned to stock markers (see the two preceding points).
The following enhancements are possible:
1. Valuation type (0VAL_TYPE)
Source field from 2LIS_03_BX/BF: BWTAR
2. Company code (0COMP_CODE)
Source field from 2LIS_03_BF/UM: BUKRS
3. Valuation area (0ID_VALAREA)
Source field from 2LIS_03_BX/BF/UM: BWKEY
4. Vendor (0VENDOR/0GN_VENDOR) - for vendor consignment stocks
Source field from 2LIS_03_BX/BF/UM: LIFNR
This is delivered with BI Content 3.3 Add-On (see SRM Business Content Online documentation).
5. Customer (0CUSTOMER) - for consignment stocks at customer
Source field from 2LIS_03_BX/BF/UM: KUNNR
6. Sales order (0DOC_NUMBER/0S_ORD_ITEM) - for sales order stocks
Source field from 2LIS_03_BX/BF: KDAUF/KDPOS
7. Project number (0WBS_ELEMT) - for project stocks
Source field from 2LIS_03_BX/BF: PS_PSP_PNR
8. Evaluation class (0VAL_CLASS)
Source field from 2LIS_03_BX/BF/UM: BKLAS (Note 684789)
Enhancement possibilities for 2LIS_03_BX:
Note that the 2LIS_03_BX DataSource cannot be extended in the same way as the 2LIS_03_BF DataSource, for example.
Only SAP can enhance this DataSource (Note 684789).
Other enhancements are no longer useful since fields, such as the movement type, G/L account or profit center do not in appear in the stock tables (for example, MARC and MARD) but only in the movement tables (for instance, MSEG).
Evaluation restrictions that occur as a result (similar to the two preceding points) can only be resolved by a data enhancement (for example, reading from a DataStore object with all material movements) subsequent to the extraction or by not using 2LIS_03_BX. In both cases, all material movements must exist in the source system. If this is not the case, you must read from the corresponding archive files for the extraction.
Changing the exception-aggregation of the stock key figures
There is a predefined exception aggregation for stock key figures (for example, "last value") in the key figure definition. If you want to override these in the query definition, proceed as follows:
-> Create a new calculated key figure.
-> Drag the relevant basic key figure to the formula area.
-> Choose "OK".
-> In the next window, choose "Extend >>".
-> Then, maintain the required exception aggregation and the reference characteristic.
Mapping FIFO logic
The data structures in the 0IC_C03 InfoCube allow FIFO logic to be mapped using the relevant query definitions. In this case, contact your SAP consultant.
Unexpected or negative stock values due to FI document summarization
If FI document summarization is activated for the MATNR field, revaluations (2LIS_03_UM) are transferred to BW without a material number. As a result, complete analyses are no longer possible at material number level. For more information, see Notes 36353 and 497992.
Options for the R/3 and BW data verification/consistency check
TAC MB5B <-> Queries 0IC_C03_Q???
(Stocks/movements R/3 <-> BW)
TACs MC.? <-> Queries 0IC_C03_Q???
(Inventory controlling LIS <-> BW)
Reports MBQUANT and RM07MMFI
(verification of the R/3 data)
Notes 739863 and 745788 provide additional information in this regard, as well as the options that exist to clean up data in BW.
With Note 766622 you can also create a LOG file for the extraction.
Archiving
See the corresponding "How to" document about archiving that is available on SAP Service Marketplace:
-> http://service.sap.com/bw
-> In the navigation area on the left: SAP BW InfoIndex
-> in the information index: A ("Archiving")
MultiProvider and non-cumulative key figures
Note 690475
Displaying the contents of the InfoCube with TAC "LISTCUBE"
Note 629451
Snapshot scenario
The "How to" document mentioned in section 2 b) "How to... handle inventory management scenarios in SAP BW 3.x" (pdf)" contains important information about the advantages and disadvantages of mapping stocks using a snapshot procedure.
Validity period of stocks
You can use transaction RSDV to determine the time period in which stocks can be calculated. This time period is determined automatically by the oldest and the most recent material movement. If you have a reporting requirement to display further stocks in the past, you can use the RSDG_CUBE_VALT_MODIFY report to manually change the time period.
Evaluations of cross-company code stock transfers.
Corresponding reports are currently not possible using the 2LIS_03_BX/BF/UM DataSources. For further information, see the following "How t"o document:
-> http://service.sap.com/bw
-> In the navigation area on the left: Services & Implementation
-> HOW TO ... Guides -> Guide List for SAP BW3.0B/BW3.1 ->
"How to... Report on cross company stock in transit", which allows you to carry out evaluations in BW similar to the ones in R/3 transaction "MB5T".
0IC_C03 data modeling
Due to the different characteristic value calculation for stock quantities and values, a MultiCube scenario ("sparse tables") is useful in this case, one InfoCube for quantities and one for values.
You can then execute common stock quantities, values and evaluations using queries on a MultiCube.
The 0IC_C03 InfoCube currently uses a key figure model (various specific key figures, such as inspection stock, stock in transit and so on). In this case, an account model is suitable:
- Three key figures: Stock quantity, stock value and valuated stock quantity (including the movement key figures)
- Based on stock instance/type, you can then limit the query to the special stock
- Advantage: Uses less database space
- Disadvantage: The load for the OLAP processor is higher and there is more work during the query definition, the other approach may also be more transparent for the end user.
Inventory management and ODS
ODS objects cannot admit any stock key figures (see Notes 752492 and 782314) and, among other things, they do not have a validity table, which would be necessary. Therefore, ODS objects cannot be used as non-cumulative InfoCubes, that is, they cannot calculate stocks in terms of BW technology.
In this connection, you should use the ODS technology only for:
- Document-related reporting or the Enterprise DataWarehouse layer based on the 2LIS_03_BX/BF/UM InfoSources (see Notes 581778 and 747037).
- The implementation of a snapshot scenario; see the How to document mentioned in section 2 b) for more information:
"How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
Implement Note 773823 to be able to update the 2LIS_03_BX InfoSource to an ODS.
If you want to activate another ODS object for the 2LIS_03_BF and 2LIS_03_UM DataSources before the 0IC_C03 InfoCube, we recommend a parallel update.
However, if you want the InfoCube to be filled by a subsequent update from the ODS, take the following into account:
Documents that are entered after the stock initialization (CPUDT field > stock initialization key date) and are posted back to a period before the stock initialization (BUDAT field < stock initialization key date),
must be updated with a delta request in the InfoCube, because only these requests can be compressed with a stock marker update.
Therefore, mechanisms for which the movements are different before and after the stock initialization (as a result of restrictions on the posting date) are incorrect in this case. However, if you want to work with the requests in question, you must restrict the movements using the date of entry (CPUDT). Otherwise the stock evaluations will be incorrect due to the compression logic used.
The same problem occurs if documents are posted to the future (CPUDT field > stock initialization key date and BUDAT field > stock initialization key date).
Posting to a prior period and postings to the future
If you can post this type of material documents in the system, take note of the documents that caused the initialization run (transaction MCNB, or report RMCBINIT_BW)during the reconstruction in R/3 (transaction OLI1BW, or report RMCBNEUA):
1. BUDAT < stock initialization key date and CPUDT > stock initialization key date
You execute the report with a date restriction (for example, upper limit = key date of stock initialization) to avoid a posting block.
-> Postings to a prior period are selected by mistake.
-> Solution: You MUST set a posting lock (if this is not possible, it may help to select according to the document number).
2. BUDAT > stock initialization key date and CPUDT < stock initialization key date
Here the same applies as described under point 1, however, the documents are then missing in the setup table. You can still make restrictions according to the posting date but you must set a relatively high upper limit.
Consumption key figures in 0IC_C03 (the same as LIS reports)
See Note 804781.
Avoiding data inconsistencies, HASH solution.
See Note 838050 for more information.
Connection between transaction keys and reversals. See Note 352344 (and an example in Note 745788).
Suppressing the display of the previous period in the BEx Web Analyzer.
See Note 623944.
6. Performance
a) General BW/logistics extraction (TSV_TNEW_PAGE_ALLOC_FAILED/ SYSTEM_IMODE_TOO_LARGE)
Notes 409641, 417307, 419465, 548845 and 589997
b) Extraction 2LIS_03_BX
The recommended setting in the RMCBINIT_BW report for 'Number of data records per LUW' is 5000. Higher values may cause the following errors:
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
TSV_LIN_ALLOC_FAILED
You can reduce an extremely long runtime by setting up the stock individually for each plant. For more information, see Note 728360.
When you run the report, the "Transfer Zero Stocks" option must NOT be active, because this will significantly increase the runtime.
This is no longer required as of Note 823951 (for more information, see Note 655798).
c) Extraction 2LIS_03_UM
Notes 537235 and 585750
d) Extraction 2LIS_03_BF
Note 454267
e) Warehouse
Due to the stock marker generation technology, it is normal for the E table to be larger than the F table in the non-cumulative InfoCubes.
As a result of the different updating of stock quantities and values (see Note 589024) required by the R/3 data model, movement data usually generates two entries in the F table.
To reduce the data volume of the 0IC_C03 InfoCube, you can distribute quantity and value key figures to two InfoCubes. As a result, the key figures have the same characteristic value update again. You can then use MultiCubes to execute common evaluations of quantities and values.
f) Queries
Notes 419490 and 784682
Message was edited by:
Jr Roberto -
Dear Gurus,
Can anyone send me the following OSS notes if u have. 567747, 130253 and 417307. Your kind help will be definitely awarded.
My mail ID is [email protected]
Best Regards
Mohan Kumar
Message was edited by: mohan kumarhi Mohan,
i think you will need to have access to oss yourself,
note 567747 is composite one that contains several notes.
sent to you mail ...
130253
Symptom
Uploading transaction data to BW takes too long
Other terms
Business Warehouse, data upload, batch upload, transaction data upload,
performance, runtime, data load, SPLIT_PARTITION_FAILED ORA00054
Reason and Prerequisites
Loading data from a mySAP system (for example, R/3) or from a file takes a very long time.
Solution
The following tips are a general check list to make the mass data upload to the Business Warehouse (BW) System as efficient as possible.
Tip 1:
Check the parameter settings of the database as described in composite Note 567745.
Check the basis parameter settings of the system.
Note 192658 Setting basis parameters for BW Systems
See the following composite notes:
Note 567747 Composite note BW 3.x performance: Extraction & loading
Note 567746 Composite note BW 3.x performance: Query & Web applications
Tip 2:
Import the latest BW Support Package and the latest kernel patch into your system.
Tip 3:
Before you upload the transaction data you should make sure that ALL relating master data has been loaded to your system. If no master has been loaded yet, the upload may take up to 100 percent longer because in this case, the system must retrieve master data IDs for the characteristic attributes and it must add new records to the master data tables.
Tip 4:
If possible, always use TRFC (PSA) as the transfer method instead of
IDocs. If you (have to) use IDocs, keep the number of data IDocs as low
as possible. We recommend an IDoc size of between 10000 (Informix) and 50000 (Oracle, MS SQL Server).
To upload from a file, set this value in Transaction RSCUSTV6.
To upload from an R/3 system, set this value in R/3 Customizing (SBIW -> General settings -> Control parameters for data transfer).
Tip 5:
If possible, load the data from a file on the application server and not from the client workstation as this reduces the network load. This also allows you to load in batch.
Tip 6:
If possible, use a fixed record length when you load data from a file (ASCII file). For a CSV file, the system only carries out the converison to a fixed record length during the loading process.
Tip 7:
When you load large data quantities from a file, we recommend that you split the file into several parts. We recommend using as many files of the same size as there are CPUs. You can then load these files simultaneously to the BW system in several requests. To do this, you require a fast RAID.
Tip 8:
When you load large quantities of data in InfoCubes, you should delete
the secodary indexes before the loading process and then recreate them afterwards if the following applies: The number of the records that are loaded is big in comparison to the number of records that already exist in the (uncompressed) F fact table. For non-transactional InfoCubes, you must delete the indexes to be able to carry out parallel loading.
Tip 9:
When you load large quantities of data in an InfoCube, the number range buffer should be increased for the dimensions that are likely to have a high number of data sets.
To do this, proceed as follows. Use function module RSD_CUBE_GET to find the object name of the dimension that is likely to have a high number of data sets.
Function module settings:
I_INFOCUBE = 'Infocube name'
I_OBJVERS = 'A'
I_BYPASS_BUFFER = 'X'
The numbers for the dimensions are then contained in table 'E_T_DIME', column 'NUMBRANR'. If you enter 'BID' before this number, you get the relevant number range (for example BID0000053).
You can use Transaction SNRO (-> ABAP/4 Workbench -> Development --> Other tools --> Number ranges) to display all number ranges for the dimensions used in BW if you enter BID*. You can use the object name that was determined beforehand to find the required number range.
By double-clicking this line, you get to the number range maintenance. Choose Edit -> Set-up buffering -> Main memory, to define the 'No. of numbers in buffer'.
Set this value to 500, for example. The size depends on the expected data quantity in the initial and in future (delta) uploads.
!! Never buffer the number range for the package dimension !!
Tip 10:
When you load large quantities of data, you should increase the number
range buffer for the info objects that are likely to have a high number of data sets. To do this, proceed as follows:
Use function module RSD_IOBJ_GET to find the number range name of the info object that is likely to have a high number of data sets.
Function module settings:
I_IOBJNM = 'Info object name'
I_OBJVERS = 'A'
I_BYPASS_BUFFER = 'X'
The number for the info object is in table 'E_S_VIOBJ', column 'NUMBRANR'. Enter 'BIM' in front of this number to get the required number range (for example BIM0000053).
Use Transaction SNRO (-> ABAP/4 Workbench -> Development --> Other tools --> Number ranges) to display all number ranges used for the info objects in BW by entering BIM*. By entering the object name determined beforehand you can find the desired number range.
By double-clicking this line you get to the number range object maintenance. Choose Edit -> Set-up buffering -> Main memory, to define the 'No. of numbers in buffer'.
Set this value to 500, for example. The size depends on the expected data quantity in the initial and in future (delta) uploads.
!! Never buffer the number range object for the characteristic 0REQUEST!!
417307
Symptom
Performance load is too high/not justifiable during data load.
Customizing settings via extractors IMG path (Transaction SBIW in the OLTP system; can be called directly in the OLTP or using Customizing, from the BW system) do not yield any considerable improvement or are not clear.
The settings in Table ROIDOCPRMS or in the Scheduler in the BW system are not taken into account by some extractors. How is the data package size defined for the data transfer to the BW? Are there application-specific features to determine the package size? If so, what are they?
Other terms
SBIW, general settings extractors, MAXSIZE, data volume, OLTP, service API, data package size, package size, performance
Reason and Prerequisites
The general formula is:
Package size = MAXSIZE * 1000 / size of the transfer structure,
but not more than MAXLINES.
You can look up the transfer structure (extract structure) in Table ROOSOURCE in the active version of the DataSource and determine its size via SE11 (DDIC) -> Utilities -> Runtime object -> Table length.
The system default values of 10,000 or 100,000 are valid for the MAXSIZE and MAXLINES parameters (see the F1 help for the corresponding fields in ROIDOCPRMS). You can use the IMG Transaction SBIW (in the OLTP system) "Maintain General settings for extractors" to overwrite these parameters in Table ROIDOCPRMS on a system-specific basis. You also have the option of overriding these values in the scheduler (in the target BW system). However, in the Scheduler (InfoPackage) you can only reduce the MAXSIZE. The advantage of using the Scheduler to carry out maintenance is that the values are InfoSource-specific.
However, some extractors have their own flow logic which MAXSIZE does not load 1:1 from the ROIDOCPRMS.
This Note does not cover all SAP applications.
Solution
Application/DataSource Standard settings or note
Generic extractor Standard (Example: Note 409641)
Delta Extraction via DeltaQueue Standard as of PlugIn 2000.2
Patch 3
LO-LIS Standard
Logistic Cockpit SD Notes 419465 and 423118
Logistic Cockpit MM-IM:
Extraction 2LIS_03_UM Notes 537235 and 585750
Extraction 2LIS_03_BF Note 454267
In general, the following applies to Logistic Cockpit Extraction: The package size set only serves as guideline value.
Depending on the application, contents and structure of the documents, and the selection in the reconstruction program, the actual size of the transfer packages may differ considerably. That is not an error.
For 'Queued Delta' update mode the package size of 9999 LUWs (=Logical Unit of Work, in this particular case documents or posting units per transaction are concerned) is set for LO Cockpit. However, if a transaction updated more than 10000 documents at once, the number 9999 would be invalid. This is because an update process cannot be split.
In the case of a 'Direct Delta' update mode there is no package size for LUW bundling. In the DeltaQueue (RSA1) every LUW is updated individually.
Also note the following:
If you want to transfer large data sets into the BW System, it is a good idea to carry out the statistical data setup and the subsequent data transfer in several sub-steps. In doing so, the selections for the statistical data setup and in the BW InfoPackage must correspond to each other. For performance reasons, we recommend using as few selection criteria as possible. You should avoid complex selections. After loading init delta with selection 1, the setup table has to be deleted and rebuilt with selection 2.
Bear the following in mind: The delta is loaded for the sum of all selections from the init deltas. Remember that the selections are made so that they do not impede the delta load, for example, if you have initialized the delta for the periods January 1st, 1999 to December 1st, 2000 and December 2nd, 2000 to August 1st, 2001 then you get a time interval from January 1st, 1999 to August 1st, 2001 in the BW. Documents from August 2nd, 2001 are no longer loaded.
CO-OM Note 413992
PS Standard or according
to Note 413992
CO-PC Standard
FI (0FI-AR/AP-3) First tables with open items(BSID for customers, BSIK for vendors) are read. The package size from the MAXISE field in Table ROIDOCPRMS is used in the extraction from these tables. If the packages are grouped together according to ROIDOCPRMS and a few data records still remain, these remaining records are transferred in one additional package.
After the open items are extracted, the system extracts from the table of cleared items (BSAD for customers, BSAK for vendors). In this extraction,the package size from the MAXSIZE field is adhered to.
FI (0FI-/AR/AP/-4 , new as of BW 30A) Like FI-AR/AP-3, but with one difference: if there are remaining records after the system reads the open items using the setting in the MAXSIZE field, they are not transferred in one extra package, but added to the first package of items read from the table of cleared items. For example, if 10 data packages with 15000 data records are extracted from Table BSID in accordance with ROIDOCPRMS, and 400 data records remain, the package size of the first data package from Table BSAD is 15400.
Both new and changed records are formatted in the following sequence in the delta transfer: 1) new BSIK/BSID records; 2) new BSAK/BSAD records; 3) changed BSIK/BSID records; 4) changed BSAK/BSAD records.
Package size 0FI_GL_4:
Prior to Note 534608 and the related notes, package size could vary considerably since the MAXLINES were applied to the document headers only. Then all documents lines for the document headers were read and transferred. As a result, the packages were 2 to 999 times as large as MAXLINES depending on the number of line items per document.
Note 534608 and the related notes changed the logic so that the MAXLINES is now also applied to the document lines. For each package, MAXLINES can be exceeded by up to 998 lines since a document is always transferred completely in one package. Smaller 'remaining packages' may also occur; for example if MAXLINES = 10000, and 10000 document headers with 21000 lines are selected, 2x10000 and the remainder of 1000 were were transferred in a separate package. Selection logic in 0FI_GL_4: Selection of the new FI documents via CPUDT -> the changed documents are then selected via Table BWFI_AEDAT. When changing the selection from new to changed documents, a package may occur which consists of the 'remainder' of the CPUDT selection and the first package of the BWFI_AEDAT selection. This package can then have a maximum size of 2 x MAXLINES.
FI-FM Note 416669
EC-PCA For the most part, the systemadheres to the standard settings but for technical reasons, packages packages smaller than the MAXSIZE or 7200 larger than the MAXSIZE may be omitted in Table ROIDOCPRMS
FI-SL as in EC-PCA
PT Standard (refer to Note
397209)
PY Standard
PA Standard
RE Standard
ISR-CAM (Category Management,
new as of PlugIn 2001.1) Standard
CO-PA During the initialization and fullupdate in the profitability analysis, a join is always read from two tables (For details see Note 392635). To avoid terminations caused by Select statements that run for too long, access occurs with intervals for the object numbers (fixed size 10,000). New intervals are read until the package size requested by BW is reached. Therefore the size of the data package is always equal to or larger than the specification, but it can vary considerably.
Master data:
Business partner Standard
Product Standard
Customer Standard
Vendor Standard
Plant Standard
Material Standard
567747
Symptom
You want to improve the performance of the extraction and loading of your data into SAP BW 3.x.
Solution
This is a composite note that deals with performance-relevant topics in the area of extraction and loading.
If you encounter performance problems, ensure that the current Support Package has been imported.
This note is continually updated. You should therefore download a new version on a regular basis.
You will find further documents in the SAP Service Marketplace, alias bw under the folder "Performance".
Contents:
I. Extraction from the OLTP
II. Loading generally
III. Master data
IV. Roll-Up/aggregate structure
V. Compression
VI. Hierarchies/attribute realignment run
VII. DataMart interface
VIII. ODS objects
IX. Miscellaneous
I. Extraction from the OLTP
Note 417307: extractor packet size: Collective note for applications
Note 505700: LBWE: New update methods from PI 2002.1
Note 398041: INFO: CO-OM/IM IM content (BW)
Note 190038: Composite note performance for InfoSource 0CO_PC_01 and
Note 436393: Performance improvement for filling the setup tables
Note 387964: CO delta extractors: poor performance for Deltainit
II. Loading generally
Note 130253: Notes on uploading transaction data into BW
Note 555030: Deactivating BW-initiated DB statistics
Note 620361: Performance data loading/Admin. data target, many requests
III. Master data
Note 536223: Activating master data with navigation attributes
Note 421419: Parallel loading of master data (several requests)
IV. Roll-Up/aggregate structure
Note 484536: Filling aggregates of large InfoCubes
Note 582529: Rollup of aggregates & indexes (again as of BW 3.0B Support Package 9)
V. Compression
Note 375132: Performance optimization for InfoCube condensation
Note 583202: Change run and condensing
VI. Hierarchies/attribute realignment run
Note 388069: Monitor for the change run
Note 176606: Apply Hierarchy/Attribute change ... long runtime
Note 534630: Parallel processing of the change run
Note 583202: Change run and condensing
VII. DataMart interface
Note 514907: Processing complex queries (DataMart, and so on)
Note 561961: Switching the use of the fact table view on/off
VIII. ODS objects
Note 565725: Optimizing the performance of ODS objects in BW 3.0B
IX. Miscellaneous
Note 493980: Reorganizing master data attributes and master data texts
Note 729402: Performance when compiling and searching in the AWB -
Unable to use Datasource.cfc in Admin API - The current user is not authorized to invoke this method
Hi Everyone,
I am having some issues accessing the methods in the datasource.cfc in the adminAPI.
I can successfully load the administrator CFC and am told that I have successsfuly logged in;
But when I try to subsequently load the datasource.cfc I get an error that the current user is unable to access the method.
/* Create an Admin API object and call the login method */
var local = {};
local.adminObj = createObject("component", "cfide.adminapi.administrator");
/* Enter your password for the CF Admin */
/* if you dump this - TRUE is returned */
local.adminObj.login(adminPassword="my_admin_user_password");
/* Create an object of datasource component */
local.dsnObj = createObject("component", "cfide.adminapi.datasource");
writeDump(local.dsnObj.getDataSources());
I tried creating separate admin users and passwords - yhinking that perhaps a revent hotfix had stopped the "admin" user from being allowed to use the adminAPI - but changing to a new adminuser yielded the same results.
I could login to the admin API with the new username and passsword - but could not access the datasource.cfc after that.
Here is the debug output from the error...
The current user is not authorized to invoke this method.
The error occurred in accessmanager.cfc: line 48
Called from datasource.cfc: line 52
Called from C:/inetpub/wwwroot/projectDir/trunk/Application.cfc: line 155
Called from C:/inetpub/wwwroot/projectDir/trunk/Application.cfc: line 52
Called from C:/inetpub/wwwroot/projectDir/trunk/Application.cfc: line 45
Called from C:/inetpub/wwwroot/projectDir/trunk/Application.cfc: line 1
-1 : Unable to display error's location in a CFML template.
Resources:
Check the ColdFusion documentation to verify that you are using the correct syntax.
Search the Knowledge Base to find a solution to your problem.
Browser
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31
Remote Address
127.0.0.1
Referrer
Date/Time
22-Apr-13 01:09 PM
Stack Trace
at cfaccessmanager2ecfc974154242$funcCHECKADMINROLES.runFunction(E:/cf10_final/cfusion/wwwro ot/CFIDE/adminapi/accessmanager.cfc:48) at cfdatasource2ecfc1679861966$funcGETDATASOURCES.runFunction(E:/cf10_final/cfusion/wwwroot/ CFIDE/adminapi/datasource.cfc:52) at cfApplication2ecfc498167235$funcPREREQUISITESTART.runFunction(C:/inetpub/wwwroot/projectD ir/trunk/Application.cfc:155) at cfApplication2ecfc498167235$funcINIT.runFunction(C:/inetpub/wwwroot/projectDir/trunk/Appl ication.cfc:52) at cfApplication2ecfc498167235._factor5(C:/inetpub/wwwroot/projectDir/trunk/Application.cfc: 45) at cfApplication2ecfc498167235.runPage(C:/inetpub/wwwroot/projectDir/trunk/Application.cfc:1 )
coldfusion.runtime.CustomException: The current user is not authorized to invoke this method. at coldfusion.tagext.lang.ThrowTag.doStartTag(ThrowTag.java:142) at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2799) at cfaccessmanager2ecfc974154242$funcCHECKADMINROLES.runFunction(E:\cf10_final\cfusion\wwwroot\CFIDE\adminapi\accessmanager.cfc:48) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:472) at coldfusion.filter.SilentFilter.invoke(SilentFilter.java:47) at coldfusion.runtime.UDFMethod$ArgumentCollectionFilter.invoke(UDFMethod.java:368) at coldfusion.filter.FunctionAccessFilter.invoke(FunctionAccessFilter.java:55) at coldfusion.runtime.UDFMethod.runFilterChain(UDFMethod.java:321) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:220) at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:655) at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:444) at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:414) at coldfusion.runtime.CfJspPage._invoke(CfJspPage.java:2432) at cfdatasource2ecfc1679861966$funcGETDATASOURCES.runFunction(E:\cf10_final\cfusion\wwwroot\CFIDE\adminapi\datasource.cfc:52) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:472) at coldfusion.filter.SilentFilter.invoke(SilentFilter.java:47) at coldfusion.runtime.UDFMethod$ReturnTypeFilter.invoke(UDFMethod.java:405) at coldfusion.runtime.UDFMethod$ArgumentCollectionFilter.invoke(UDFMethod.java:368) at coldfusion.filter.FunctionAccessFilter.invoke(FunctionAccessFilter.java:55) at coldfusion.runtime.UDFMethod.runFilterChain(UDFMethod.java:321) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:220) at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:655) at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:444) at coldfusion.runtime.TemplateProxy.invoke(TemplateProxy.java:414) at coldfusion.runtime.CfJspPage._invoke(CfJspPage.java:2432) at cfApplication2ecfc498167235$funcPREREQUISITESTART.runFunction(C:\inetpub\wwwroot\projectDir\trunk\Application.cfc:155) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:472) at coldfusion.runtime.UDFMethod$ReturnTypeFilter.invoke(UDFMethod.java:405) at coldfusion.runtime.UDFMethod$ArgumentCollectionFilter.invoke(UDFMethod.java:368) at coldfusion.filter.FunctionAccessFilter.invoke(FunctionAccessFilter.java:55) at coldfusion.runtime.UDFMethod.runFilterChain(UDFMethod.java:321) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:220) at coldfusion.runtime.CfJspPage._invokeUDF(CfJspPage.java:2659) at cfApplication2ecfc498167235$funcINIT.runFunction(C:\inetpub\wwwroot\projectDir\trunk\Application.cfc:52) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:472) at coldfusion.runtime.UDFMethod$ArgumentCollectionFilter.invoke(UDFMethod.java:368) at coldfusion.filter.FunctionAccessFilter.invoke(FunctionAccessFilter.java:55) at coldfusion.runtime.UDFMethod.runFilterChain(UDFMethod.java:321) at coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:220) at coldfusion.runtime.CfJspPage._invokeUDF(CfJspPage.java:2659) at cfApplication2ecfc498167235._factor5(C:\inetpub\wwwroot\projectDir\trunk\Application.cfc:45) at cfApplication2ecfc498167235.runPage(C:\inetpub\wwwroot\projectDir\trunk\Application.cfc:1) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:244) at coldfusion.runtime.TemplateProxyFactory.resolveComponentHelper(TemplateProxyFactory.java:538) at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:234) at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:159) at coldfusion.runtime.TemplateProxyFactory.resolveFile(TemplateProxyFactory.java:120) at coldfusion.cfc.CFCProxy.<init>(CFCProxy.java:138) at coldfusion.cfc.CFCProxy.<init>(CFCProxy.java:84) at coldfusion.runtime.AppEventInvoker.<init>(AppEventInvoker.java:64) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:232) at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40) at coldfusion.filter.PathFilter.invoke(PathFilter.java:112) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:94) at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:79) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28) at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62) at coldfusion.CfmServlet.service(CfmServlet.java:219) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:928) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:414) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:204) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:539) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:298) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)
And here is the listed exceptions, beneath the stack trace;
13:09:56.056 - cfadminapiSecurityError Exception - in E:/cf10_final/cfusion/wwwroot/CFIDE/adminapi/accessmanager.cfc : line 48
The current user is not authorized to invoke this method.
13:09:56.056 - cfadminapiSecurityError Exception - in E:/cf10_final/cfusion/wwwroot/CFIDE/adminapi/accessmanager.cfc : line 48
The current user is not authorized to invoke this method.
13:09:56.056 - java.io.FileNotFoundException - in C:/ColdFusion10/cfusion/wwwroot/WEB-INF/exception/errorcontext.cfm : line 44
E:/cf10_final/cfusion/wwwroot/CFIDE/adminapi/accessmanager.cfc (The system cannot find the path specified)
This perspn seems to be having the same issue;
http://forums.adobe.com/message/5051892
and I agree I don't have "E" drive either!I've found a solution to my plight - I don't know if it'll work for you or help you try something that MAY fix it.
I use a common code set which includes the Application.cfc from a CF Mapping - So, in the application.cfc in the actual website I do this:-
<cfinclude template="/UberDirectory/Application.cfc">
Then, in the /UberDirectory/Application.cfc, I was initialising a CFC which checks if the datasource was created for the website. The datasource checking code attempts to log into the Admin API and check & create if necessary the datasource.
This has previously worked without fail for me - But in this instance it failed!! I was doing two things wrong - Firstly, the CFC should only be called in the Application.cfc in the onRequestStart section as the Application had to be initialised first - This is maybe because I've invoked the application.cfc in a "non-standard" manner.
Secondly, once I'd moved the CFC invocation into oNRequestStart I saw the following error:-
The string COOKIE.CFAUTHORIZATION_uber-directory is not a valid ColdFusion variable name.
I had this as the app name .... <cfset this.name = 'uber-directory'>
Changedthe dash to an underscore and I was away and could once again check the datasources
Hope it helps
Martin -
Is there a way to transfer or copy all my apps to another iPad with a different account? I was required in my job to use the one at work, but I would like to also see my current set ups and apps as in my personal one. Thank you so much!
What I suggest is that you try to pair your apple ID with you company ipad and see if it works.
Here is why::
I believe that the Apple rules let you. They are something like:
-- for a shared iDevice, you may put the app on one device
-- for a device you use exclisively, you may put the app on five (or some number) of iDevices
I'm not lawyer, so how you interpred this is a question.
Now, you need to figure out how to do this.
In the past at least, apple used this terminalogy.
Personal
Institution
Layered. combines personal & institution.
It depends on how your company has configured the iPad.
I have read where you can have upto three apple id per device. -
Clarification about OSS note 677377 - E-mail to credit representative
Hello,
in the OSS note mentioned in the subject I find the following statement: "The document can be released directly from the e-mail".
I have this question: the option to release the document from the e-mail is available only if the workflow is active?
I made all the settings mentioned in the OSS note but I receive in SAPoffice only the notification with no option to release the SO.
Thanks and best regards,
AndreaHi,
try the following:
open your workplace in SAP office and go to inbox folder. Click on unread or read documents and documents will be displayed on the right side of the screen. Select one of the documents and click on right button of the mouse and click on execute. You´ll execute the tcode you set in execute parameters on your message.
Regards,
JM -
OSS Note for MIGO "Update terminate (SAPSQL_ARRAY_INSERT_DUPREC)"
Dear all
I am facing problem during MIGO GR reference Others, MVT 561.
Upon clicing Button: Save, I face 2 types of errors intermittently
1. Material document is saved and generated but when comes to displayed, it will say "Document 4900496xxx does not exist in calendar year 2009" And I check in Table: MKPF and it does not exist at all
2. I am not able to save it and face this termination error:
The ABAP/4 Open SQL array insert results in duplicate database record
What happened?
Error in ABAP application program.
The current ABAP program "SAPLGLIU" had to be terminated because one
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and adminis
termination messages, especially those beyond their normal deletion"
I have done my investigation and the number range uder FBN1 for this MVT 561 under this Company Code and Year has been maintained.
Can anyone advise me the OSS note to solve it? I cannot find a direct OSS note on it to solve this.
Thanks.
Edited by: Daimos on Oct 26, 2009 7:58 AMSorry Jurgen
I have posted so many material documents using MIGO to test it out and try to update my OMBT there so many times until I lost track what is the current number range when I wrote my question here.
I have read that thread you posted regarding the ST22 analysis [Solution from Jurgen|Document does not exist after creation of PO; . I exported them to HTML and did a detail checking, and I find out it is FI GL there did not update the number range properly which in turns cause my GR to have problems.
Below is my analysis and learning to share with others:
1. Ask the ABAPER to find out which record value the system trying to insert. Copy down this number.
2. Check the OMBT value of Current Number.
3. Then use the MFPK Table to search the latest Number Range.
4. Try to check if the record value trying to insert already exists in Current Number. Normally, it will exist and that is why
system prompt "insert duplication".
5. Then check if the record value trying to insert already exists in MFPK Number. Normally, it will exists it will exist and that is
why system prompt "insert duplication". (There can be situation that the Current Number is lower than the MFPK Number,
but it rarely happen).
6. Replace the Current Number to be the Next Number of MKPF largest Number. Save and it should work.
7. If it is not work, please create a material which is non valuated and perform GR, if GR can be done and we can display
material doc, it means the error is caused by the FI GL number range error.
8. There can be other issues such as activation of user exits and other.
Jurgen, I got one more question to ask you. I have tried to replace the current number with the largest number of MKPF without + 1. It can solve my problem.
But I wonder why SAP Notes and you suggest us to replace Current Number with largest MKPF value PLUS 1?
Please advise.
Thanks.
Edited by: Daimos on Nov 2, 2009 8:41 AM
Maybe you are looking for
-
My iPhone 4s has been replaced at least 4 times within a year and nobody at the genius bar seems to know what's wrong but every time I plugy phone into my cable that connects my iPhone to the stero in my car and when I disconnect it, my iPhone think
-
How to update Records of SAP table from .CSV file
Hi, I have written a code which takes a data from (,) delimited CSV file and adds it into the Internal table. Now I want to update the all fields in SAP table with the Internal table. I want to use Update statement. Update <table Name> SET <field nee
-
How to change colors settings -- newbie to mac
I was messing around with the settings and selected to polarize the image so that it looks like a photo negative. I feel like a moron so far in using the mac and i cant find how to switch it back to normal. Any help is appreciated.
-
Hi, I need help . I have an application in Sun Java Application Server in SOLARIS, that contain an image with cewolf. But the image do not appear in the application. I tried in windows and the image appear well. How I do to the image appear?? Please
-
I am using RoboHelp 7 but I have had this problem with every version of RoboHelp. I generate a Word file from RH, clean up the Word file and then generate a PDF file from the Word file. Some of the PDF bookmarks have an extra space before the first l