Archiving: Info-structures and field catalogues

Hi there.
My question concerns the field catalogues which are used to configure info-structures for archiving objects.
As far as I understand it, I can only run reports via the Archive Explorer on the fields which I have included in the info-structure for an archiving object - is this correct? Or can I only use the fields in the info-structure for selection, but display all fields available in the archive-object?
As a last question: Can I create field catalogues with theoretically all of the available fields of an archiving object?
Thank you very much.
Andreas

Hello Andreas,
The fields that are transferred from the field catalog into the infostructure are used to assist with selecting the relevant archived data. The infostructure will contain the fields that have been transferred, plus the archive file name and the offset of where the archived data is stored. This gives you access to all of the data that was archived.
Technically, you can create a field catalog and relevant infostructure with all of the available fields, but I would not recommend that approach. The infostructure is a table in the database. So, the more fields that are used, the bigger this table will become and may defeat the purpose of archiving the data in the first place :-).
I hope this helps.
Regards,
Karin Tillotson
Message was edited by: Karin Tillotson

Similar Messages

Archive info structures

Hi,
There is a standard archive object FI_MONTHLY. In table AIND_STR1 (archive info structures), I could see that there are 5 info structures( SAP_FI_MONTH_01 to SAP_FI_MONTH_05) corresponding to this archive object FI_MONTHLY.
But, using SARJ transaction, if the info structure SAP_FI_MONTH_01 is given, it is saying that ' Info structure SAP_FI_MONTH_01 does not exist .Do you want to create SAP_FI_MONTH_01? '.
Please suggest what could be the problem.
Thanks in advance,
Vishnu Priya

Hello Vishnu,
If you check AIND_STR1 again, you will notice that the 5 entries for archive object FI_MONTHLY are type "S" for Field Catalog. You will need to create the actual archive information structure based on one of the 5 field catalogs.
Please let me know if you need additional information.
Regards,
Karin Tillotson

Difference between Info structure and Table

Hi Friends
I need to know difference between info structure and table (updating a table using a scheduled program),Which one of this is better and why?
Please help me to get the Pros and Cons of the two available approach.
Thanks
Mitesh

Hi,
No different, these are just transparent tables like any other. You can select data from them the same as any other transparent table.
Refer
https://forums.sdn.sap.com/click.jspa?searchID=4342729&messageID=1424611
https://forums.sdn.sap.com/click.jspa?searchID=4342729&messageID=3609095
Regards

Need your assistance in mapping Structure and Field in DME Tree

Hello Friends - I need your help in "Mapping from structure field" in DME.
In the existing format tree, It is mapped Structure as "FPAYP" and Field name "BNAME" to populate Company Code name in the Payment file.
Now I am asked to change this to populate value either from OX02 or OX15.
When Company Code name was maintained, It was maintained in short and in the address tab, Full name is maintained.
Please let me know which Structue and Field I should assign to pull the value either from OX02 or OX15.
Thanks for your help.

Thanks a lot Henri/Lakshmi.
I have maintained mapping procedure Sturecture/field - FPAYHX/AUST1 to get the CoCd name in the file. In AUST1, Length of the CoCd is more than 18, and as per Bank format, It should be 18 characters in length.
User is not happy that complete CoCd name is not populated in the file. He has come up with an alternative and shortened the CoCd name that needs to be populated in the file and suggested us to get the value into the payment file. We should not replace CoCd name with the name he suggested in OX02/OX15,FBZP.
My doubt is that if there is any filed I can use to maintain the name he suggested and assign it in mapping procedure.
Thanks

CProjects Fields - Structures and field Controls

Hi,
On the Project -Additional Data tab on cProjects, we have a field which is called Project "Created by". I am trying to locate where is that field stored in the tables. I saw that under the field controls ,an external structure is maintained and this feild is available there but not sure how to view the data in that structure ( i guess we can't view this data as its under a structure).
Since we have the accounting integeration on, so when we transfer the Project ,the Projects gets created in the backend ( ECC) with a "created by" of the repsective cProjects server name.
All I am looking for is who created the Project ( as in cProjects) and the date on which it was created.
Thanks.

Hi,
The structure is DPR_TS_UI_PRJ_DATA.
If you need to get the values you should use method get_detail_data of class cl_dpr_ui_log_project_detail.
Regards,

Info structure S021 and S022

Hi all,
There are no table entries in these information structures. What needs to be done to update these tables ? Other table (e.g. AUFM)
are getting updated.
Regards,
Yogesh

Hi,
For your order types in OPL8 under implementation tab, the Shop Floor Information Systems -> Statistics should be checked.
Now go to OMOD select the info structure and set to asynchronous update.
Regards,
Vivek

Problem with Self defined info structure.

Hi All,
We have Create some Self define Info structure Like ;--
S061 Location and Planning               --->S501
S062 object class and manufacturer --->S502
S063 Danage analysis                        --->S503
S065 Object Statistics                         --->S504
But probleme is when we excute S501 self defined info structure heading comes as
Standard Analysis for Info Sstructure S501: Selection where as in Standard it is coming as Location Analysis: Selection
Any one can tell how can i solve this probleme.
Thanks
Vinit

steps to create own infostructure by copying standard infostructure.
steps.... 1) First Create your own info structure using menu path SPRO> Logistics general > LIS > Logistics data warehouse > Data basis > information structure > maintain self defined ino structure Here create a New stucture called S901 (Follow Custom defined structure naming conventions) for application 07, by copying S115 .
Once inside this Choose the Charateristic button below and CHOOSE SELECTION LIST.
This will popup a list of fields that can be added to the structure for analysis per field catalogue.
Navigate to the notification Object field catalog to select the Order number.
Select other field as appropriate from other field catalog and copy them.Then select or de-select the "Key figures" thats relevant for your needs Check ,generate and activate the same structure and save.
2) Create Update rules for updating this info structure by copying the rules of S115.
SPRO> Logistics general > LIS > Logistics data warehouse > Data basis >Updating > Specific definition using update Rules > Maintain update rules.
Enter the newly created Structure name and choose teh Update group 26 (use drop down) and enter the S115 and 26 as teh group and rules to copy from.
Delete the rules thats not relevant for your needs and then check, and Choose "generate: and then activate the "UPDATING" and save.
3) Activate the Update type for the new structure. SPRO> Logistics general > LIS > Logistics data warehouse > Data basis >Updating > Update Control > Activate Update.
Choose PM and double click on the new structure that you had just created and chosoe Period and Type of updating (2: Similar to other standard info structures). and save.
This should start updating New orders that you are creating from Now on.
However if you would like to pre-populate existing data in this structure for analysis, then you would have to run through the generation program in background for this specific structure.
SPRO> Logistics general > LIS > Logistics data warehouse > Data basis >tools > setup of statistical data >Application specific setup of statistical data > perform setup - PM.
Here make sure to do the PMIS statistical setup (This might be redundant, if you havent changed any value category that updates PMCO table) and Set Up: Plant Maintenance IS(Make sure to choose your specific structure).
You should be able to check the table entries to confirm that the program has updated the table (Name of the info structure).
The defaulted version could be different from the standard version (000).You could copy the data from one verion to another version using the first step in this block.
Once the genration is complete you should be ready to use this structure using MCIS transaction (PMIS > Standard analysis > User defined analysis).
This will list out all the user defined structures and you can pick and execute the one that you had just created.
Regards
Dhiren
Edited by: Dhiren Kumar Sahoo on Feb 2, 2010 3:55 PM

Info structure in not updated

Dear all,
I am creating one info structure containing Customer Group is added to characteristics.
But when i am updating the info structure then it dosenot update.
Can u plz send me the detail customization for creating new infostructure.
Also why it is not updating?
Plz sent me the details regarding the same.
Thanks & Regards,
PM

Goto OMO1 tcode and select ur info structure and double click on it and sel;ect the radio button "synchronus updating" and check.
compare ur settings with the below configuration.
please gothough this config
IMG menu path for SIS: IMG>Logistics General>Logistics Information System (LIS)
Figure 1: IMG menu path for SIS configuration steps
Task 1: Create Self-Defined Information Structure
Use transaction code MC21 (menu path Logistics Data Warehouse>Data Basis>Information Structures>Maintain self-defined information structures> Create) to create a Self-Defined Information Structure. Give a customer-range number 990 (any available number between 501 and 999). To make it easier, use copy from to copy structure from S001.
Figure 2: Create a Self-Defined Info Structure
Figure 3: Structure S990 is created as a copy of S001
Structure S990 is created as a copy of S001. Accordingly, you will see defaulted characteristics and key figures. Review various settings (unit, sum, etc.).
Add two more characteristics: Sales Order Number and Item Number.
Click on Choose Characteristics Icon and then click on Selection List icon to choose fields from field catalogs.
Choose field catalog SD: Bus transaction (order) by double-clicking it. Double-click on Sales Document and Sales document item from field catalog fields (you may need to scroll-down).
Figure 4: Choose fields Sales Document and Sales Document Item from Field Catalog
You can view technical names by toggling the Switch Display icon.
Figure 5: Switch display to view technical names
Make sure that you have selected correct characteristics as: MCVBAK-VBELN and MCVBAP-POSNR.
Click on Copy + Close icon and then click on Copy icon to accept the changes.
Review information
Double-click on characteristics and key figures to review technical information. This step is not mandatory, just for information.
Figure 6: Review technical field information for characteristics: Customer (KUNNR), Sales Order (VBELN), Item (POSNR) and Key figures: Incoming Order (AENETWR), Open Order (OAUWE)
System displays the generation log.
Figure 7: Generation log for Structure S990. Table S990E is Structural Information for Table S990
Task 2: Maintain Update Groups
SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>General Definition Using Update Groups>Maintain Update Groups
Figure 8: Update Groups for Sales and Distribution
No new entries need to be created. You can use the existing system-delivered update groups. Use Update Group (UpdGrp) 1 for the standard order process of: SIS: Sales Document, Delivery, Billing Document and use UpdGrp 2 for the SIS: Returns, Returns Delivery, Credit Memo.
Task 3: Maintain Update Rules
SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>Specific definition using Update Rules>Maintain Update Rules>Display
Info Structure S001 and Update Group 1.
Before we create update rules for S990, let's review how update rules are defined for S001. Review rules for Characteristics and key figures.
Figure 9: Update Rules for combination of Structure S001 and Update Group 1
Double-click to review specific details of the update rule for Key Figure Incoming Orders. Note that the event is VA Sales Order creation.
Figure 10: Update rules for Key Figure Incoming Orders
Figure 11: Characteristics for Incoming Orders
Similarly review details of Key Figure Sales. Note that the Invoiced Amount (Sales Amount) is updated by event VD Billing Document.
Figure 11: Update rules for Key Figure Sales
Figure 12: Characteristics for Sales
Similar to Update Rules of S001, we need to create Update Rules for our Self-Defined Structure S990.
SIS IMG>Logistics Data Warehouse>Updating>Updating Definition>Specific definition using Update Rules>Maintain Update Rules>Create (transaction code MC24). To make it easier, use copy from to copy update rules from S001.
Figure 13: Create Update Rules for Structure S990
Please make sure the Source information is properly updated for all the characteristics. Since you copied the rules, the sales order and item rules are defaulted too. Make sure appropriate changes are made for events VC (delivery) and VD (Invoice).
Figure 14: Source Characteristics for Sales Document and Item
Since we copied the Update Rules, the source field and table information is also copied. We need to change appropriately to make sure correct source information is populated. Click on Rules for charact and verify source information for every key figure, by clicking on previous key figure and next key figure.
Figure 15: For Event VD Billing Document, Sales Document and Item are present in MCVBRP table
Figure 16: For Event VC Shipping, Sales Document and Item are present in MCLIPS table
Figure 17: Maintain Update Rules for Structure S990 and Update Group
Task 4: Maintain Statistics Groups
Maintain Statistics Groups
Maintain Statistics Groups for Customers, Materials, SD Document Types etc. Most of the pre-defined settings are enough. Make sure that settings are updated for customized objects too, e.g., SD document types for your organizations.
Also, make sure that the customer (sales view) and material Master records are updated with appropriate Statistics Groups.
Figure 18: Maintain and assign statistics groups. IMG path: Updating> Updating Control> Settings: Sales> Statistics Groups
Maintain Statistics Groups for Customers (OVRA)
Figure 19: Statistics Groups for Customers
Maintain Statistics Groups for Material (OVRF)
Figure 20: Statistics Groups for Materials
Maintain Statistics Groups for Sales Document
Figure 21: Statistics Groups for Sales Documents
Assign Statistics Groups for relevant Sales Document Type
Figure 22: Assign Statistics Groups to relevant Sales Documents
Assign Statistics Groups for each Sales Document Item Type
Figure 23: Assign Statistics Groups to relevant Item Categories
-Assign Statistics Groups to each Delivery Type
Figure 24: Assign Statistics Groups to relevant Delivery Types
-Assign Statistics Groups to each Delivery Item Type
Figure 25: Assign Statistics Groups to relevant Delivery Item Categories
Determine Billing Document Types Relevant to Statistics
Figure 26: Assign Statistics Groups to relevant Billing Types
Note: As mentioned earlier, most of the settings are already set in standard system. Make sure that customized objects specific to your company are also updated appropriately.
Update Customer Master for Statistics Relevancy
Transaction Code XD02 (Sales view, field Cust stats.Grp)
Figure 27: Assign Statistics Groups to Customer Master Records (Sales view)
Update Material for Statistics Relevancy
Transaction Code MM02 (Sales 2 view, field Matl statistics grp)
Figure 28: Assign Statistics Groups to Material Master Records (Sales view)
Task 5: Assign Update Groups to Header and Item Levels
Assign Update Groups on Header and Item levels
For combinations of Sales Area (Sales Org, Distribution Channel, Division), assign Update groups (transaction codes OVRO and OVRP).
SIS IMG>Logistics Data Warehouse>Updating>Updating Control>Settings: Sales>Update Group
Update Groups at Item Level
Figure 29: Update Groups at Item Level
Figure 30: Update Groups at Item Level - details
Update Groups at Header Level
Figure 31: Update Groups at Header Level
Figure 32: Update Groups at Header Level - details.
Task 6: Activate LIS Update
Lastly, Activate LIS Update for the Structure (transaction code OMO1)
SIS IMG path: Logistics Data Warehouse>Updating>Updating Control>Activate Update>Choose Activity as Sales and Distribution.
Let's update our LIS structure S990 with period as Month and update option of Asynchronous Updating (2).
Figure 33: Activate LIS Update for S990
Finally u go through t.code MCSI, select ur info structure. Then execute the LIS report.
rewards if it helps
Edited by: kishore gopala on Feb 14, 2008 6:43 AM

Adding new key figure in Info structure

Hi all,
I am in a need to add a new key figure to our info structure here in my company.
The way I understand it is, it would be best to create a NEW info structure and copy all existing key figure and characteristic and then insert my new key figure into this and rewrite the macro if required.
So my question is
1. How to determine which info structure is currently in use in my company? If i check in MC89 - the key figures match what is in Info structure S076. So is it safe to assume that we are using standard S&OP in my company? Is that a correct way to identify the currently used info structure?
2. For our KMAT, when i open a planned order I see that there in another info structure (not S076) under configuration tab. So can we have diff info structure in use at a same time ?
Please guide.
Thanks,

Hi Nisha,
1. First of all, How would I determine which info structure is being used at this time in my company?
I need to know this so that when I am creating my own custom (S500 - S999) info structure, i can copy the existing KFs and Characteristics and add them to my info structure and then Add a specific key figure on top of that.
Info structures are nothing but tables so in se16 you can check which are Info structures are having update values.
Yes you can add the specific key figure on existing self defined info structure in MC22 after that you need to generate it.
2. Can multiple info structure be in 'use' at the same time in any scenario?
For self defined info structure are application specific you can not have multiple info structure for same scenario. If you take the example of flexible planning with self defined info structure then you can transfer the demand from only one info structure.
Regards,
R.Brahmankar

Info structure lacks the necessary structure - MA004

Dear friends,
I have created user defined Infostructure. Maintained the planning parameters by T code MC7F.
While creating a planning Hierarchy (MC61), I am getting following error.
Info structure S556 lacks the necessary structure.
Message No - MA004.
Can anybody tell me what it is?
Regards,
Avinash

The default units of the information structure on which your planning hierarchy is based are defined in Customizing (in Set parameters for info structures and key figures). They are:
·        Period indicator
·        Currency
·        Base unit of measure
The base units of measure of materials are taken from the material master records. If the base unit of measure if a material is different than the base unit of measure of the information structure, you must define the base unit of the information structure as an alternative unit of measure in the material master record
I am not sure whether it works or not, Please try.
Regards
Ratan

Self defined LIS info structure

Hi Experts,
I would like to create an info structure S501 including the following characteristics and key figures.
Characteristics:
Region
Country
Sold-to Party
Material
Key Figures:
Prod. Alloc. Qty
Incoming Order Qty.
I got problems when specifiying update rules. Any hints for it? I don't know what to do with it. Thanks.

Hi Macy,
You can go to transastion code MC9C and enter your self-defined info structure and version. The system will generate automatically a standard analysis program report for above info structure.
From here you can check the program name etc.
Also check this link for more detail about LIS.
http://help.sap.com//saphelp_erp2004/helpdata/EN/a5/6319e743a211d189410000e829fbbd/frameset.htm
Hope this will help.
Regards,
Ferry Lianto

Change info structure

Dear all,
If i want to add some new drilldown/selection criteria in an existing info structure in the system, what should i do in configuration? Do i need to change the info structure and re-activate it again (update the historial data again)? Is there any risk if I go to change the info structure?
Can anyone help me?
Best regards,
Chris

Hi,
You will not loose the Updating rules.
You will loose only all the data in the infostructure, Namely chracteristic values and Key figure Values.
Basically the Table gets restructured while regeneration so will lose all the data.
Use MC8Q for Copying
regards
Ratan
Edited by: Ratan on Jul 24, 2009 7:03 PM

Info structure validation

Dear All,
If i have created one info structure and active them. Now data is not coming info structure S813 which is copied from S039. How to activate this. Is there any impact on other info structure or stock inconsistency. Please tell me pre-requisite and impact areas.
Regards
Sanjeet Kumar

Refer the below OSS Notes it may help you..
483735 - Self-defined info structures with reference S031, S032, S039
79545 - Information structure S039

Enhance Standard Info Structure SAP_CRM_ACT to add custom fields in CRM Activity archive Search

Hi All,
We have a requirement where we need to enhance CRM UI archive search with custom fields for CRM activity Object CRM_ACT_ON. As per my analysis Standard Archive Search for activity Uses info structure SAP_CRM_ACT for searching archived data.
But when we are trying to add custom fields into above field catalog, it is treated as modification. But Modification is not allowed in our landscape.
Standard infostructure is harcoded in SAP standard method ARCHIVING_READ of class CL_CRM_REPORT_ACC_DYNAMIC which is called as part of the process. So we are not able to go ahead with custom info structure.
Can you please le me know if there are any alternative way to meet above requirement or I have missed any steps.
Thanks & Regards,
Sujit

Hello Thomas,
Maybe this link can help.
add new field to search criteria and result.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0747ac2-ffd9-2910-de9a-8a3dc44da8b4?QuickLink=index&overridelayout=true&12966506314316
Search Options - Knowledge Management - SAP Library
regards,
Grace

Info structure activation problems in data archiving

Error in info structure ARCH_IS_DSSCOPA analysis program in line 412
Message no. Q6227
Diagnosis
There is a syntax error in line 412 of the generated reporting
program for the archive information structure ARCH_IS_DSSCOPA.
The error message is: Field "AINT01" already defined ...
Field "AINT01" already defined
Procedure
It is probably caused by a system error. The following activities may
solve the problem:
Check the definition of the archive information structre and the underlying field catalog.
You should contact the SAP Hotline if the problem appears for an SAP- standard info structure or an SAP-standard field catalog.
Further notes
Alternatively you can find a program whose name begins with "GP$ERR$" (search with "GP$ERR$*"). This program contains the incorrectly generated code.
Kindly let me know , how to activate the same.
Regards,
BALAMURALI JAMPANI

Hi,
This forum is for SAP Business One users only. Please check the subject of the forum. Post it on a proper forum and close this one.
Thanks,
Gordon

Archiving: Info-structures and field catalogues

Similar Messages

Maybe you are looking for