I've created a custom infostructure and field catalog in SARJ but when I try and transport the changes it fails to update the Infotable for the structure in the next environment. Is there something I'm missing?
Request clarification before answering.
OK, thank you for your help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ron,
From my point of view, a ZARIX table should not be used in SQL statements and CDS views because the name of the table can be different on each system,
The data of an info structure should be read with the function module AS_API_READ.
If the table should have the same name on all systems, then you must activate all info structures of an application (e.g. MM) on all systems in exactly the same order.
Best regards,
Andreas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then how would you work with anything pointed at those table tables like a CDS view? You would have to move/activate everything then alter the CDS views secifically for the next environment rather than development?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ron,
the structure table and the report program are not transported. They have to be generated on
the target system.
You have to
perform the following steps on your test system ST2 (transaction SARJ):
- Archive Infostructure
/ Deactivate
- Utilities / Delete
Program
- Utilities / Delete
Tables
- Archive Infostructure
/ Activate
Afterwards you
have to fill the infostructure (transaction SARI).
During this time, the archived data cannot be accessed and depending on the data volume, loading the data may take some time.
Activating and
Deactivating Information Structures
https://help.sap.com/docs/SAP_NETWEAVER_750/f0944a4717b5464f8d2343f9a44ff65b/4d8c77d8910b154ee100000...
Archive
infostructure customizing when active
https://answers.sap.com/questions/13207330/archive-infostructure-customizing-when-active.html
Best regards,
Andreas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
does it not bring over the Zarix table and report from the lower environment?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for the delay in getting back to you. From SARJ I have made changes to a custom infostructure in with an updated field catalog and structure table. I attach all three pieces to a transport using solution manager and then in the test system I use STMS_Import and select the options to overwite things but when i go to SARJ in the test system I still see the original values and not the transported changes. in the screenshot below DEV is on the left and Test is on the right

Here is the screenshot of the import log

Thanks for trying to help with this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
probably you didnt activate the infostructure after it was transported .
activation creates the ZARIX* table & generates the report .
or
did you try activation & it showed some errors?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ron,
Could you please describe the issue in more detail (error messages, screenshots)?
Was the transport request imported successfully in the target system?
Is the new field catalog and new structure available in the target system (transaction SARJ)?
As already mentioned by Satya PRASAD, have you activated the new structure in the target system?
Have you filled the archive info structures with data from the archive?
Best regards,
Andreas
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.