Report Group 1SIP Consistency Check

SAP reccomends the following to be consitency check for CO customers for system copy:
"CO customers: An additional consistency check can be performed by running the report group 1SIP before the system copy in the source system, as well as after the copy in the target system, and then comparing the results. No customer data may be changed in the meantime."
I have the following question:
1. By "Running the Report Group" does SAP mean running the individual reports under the Report Group 1SIP?
Edited by: Asim M on May 23, 2008 6:49 PM

Hi,
Yes, that is what is meant, i.e. report 1SIP-001 or TA S_ALR_87013611. In this case report group and report are synonymous as there is only one report assigned to the 1SIP report group (customer reports should never be assigned to SAP standard report groups). Therefore running 1SIP via TA GR55 results in the same output.
Regards
Karl

Similar Messages

Connection dropped between DPM and Agent during consistency check, following DPM 2012 SP1 to DPM 2012 R2

Recently I have updated a DPM 2012 SP1 standalone server to DPM 2012 R2. That it’s self was a challenge... Following the upgrade most of the protection groups required consistency checks. For some time I have been having problems performing these consistency
checks on remote servers over a 10Meg link.
On the DPM server I would kick off a ping to the remote host, then start a consistency check. Within a few seconds I would start to get dropped pings, and very large ping response times, 3000ms plus. Within 3 minutes the pings would time out completely and
no connections can be made to the remote server, RDP etc. However any other server on the network can connect to the remote client. Eventually the DPM jobs times out and sometime later the pings also return.
The resolution to this has taken some digging but this is what I have found. The DPM agent update does not seem to fully work and requires a reinstall. Here is my process:
Logon to remote client server
Install .net 4 (a raw install of the client requires this, may not be needed when done via DPM)
Via Add Remove Programs, remove DPM agent
Clean up Reg
Delete "HKLM\SOFTWARE\Microsoft\Microsoft Data Protection Manager"
Delete "HKLM\System\CurrentControlSet\Services\DPM**" (However this key is not there for me)
Back onto DPM Server
Modified protection groups as required to remove all instances of the client server
Remove Agent for client server
Install agent via DPM (watch for the glitch right at the end where it does a failed, then succeed…)
REBOOT client server
Add back into protection group
Consistency check kicked off automatically
This seems to have fixed the issue.

Hi,
The prerequisite required for DPM 2012 SP1 that must be installed is a re-rerelease of UR3 which is 4.1.3317.0 - please download and install the update specified.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Report Group in Report Painter

In my report group there are many reports .
Now i need to give a transaction code to my report group.
Then which report will execute by the transaction code

Hi
To create a Transaction Code for a Report Painter/report writer report
Tcode for Report Painter
To create a TCode, follow the steps below.
1) Go to Transaction code SE93, Enter TCode Name and Press Create.
2) Give short Description and select Parameter Transaction, Press Enter
3) Select Transation Radio Button and write START_REPORT in the next text
box Also Check the box Skip Initial Screen.
4) On the bottom of Screen (default Values), Enter Parameters
i) Name = D_SREPOVARI-REPORTTYPE. Value = RW
ii) Name = D_SREPOVARI-REPORT Value = Your Report Group Name (Say 1SIP)
5) Save and Execute.
Reward points for useful Answers
Regards
Anji

SELS error during consistency checks. Fieldname not found in sender

I'm stuck in the System Analysis section, after starting programs for Generation and Reveiver settings. The task "Execute Consistency Checks" returns an error in PC001_PCL_CHECK.
Check SELS started at 16.06.2011 14:38:31
Errors detected for conversion object A910 :
A910:Fieldname VKORG of structure S_A910 mentioned in selref not found in sender
Check SELS finished at 16.06.2011 14:39:00
The help says:
The selection field mentioned for the reduction of this conversion object does not exist in the sender system. Thus this selection field can not be used for reduction. Please remove the assignment of this conversion object from reduction. For further assistance please contact SAP support.
My question is simply HOW? Where can I remove this object? I don't even find a structure called S_A910 in any of my systems. I have table A910 but it doesn't have a field called VKORG in it at all... I'm somewhat lost here.
I've added the latest SPs (17) and also applied all the notes. At least I think I applied them all... I repeated the step several times, no luck.
Any ideas?
Thanks in advance
Stefan

Hi Sandeep,
Many thanks for your reply. The note hasn't fixed the issue so I'm still stuck with the exact same error. I did run it as described and while the report updated a few fields, it didn't help to eliminate the error. Reading the note it would appear that the error described there is different from what I'm facing.
> error message like : "TVKOV: member ID_VKORG of group G_VK has no selref field!
I am getting "Fieldname of structure S_A910 mentioned in selref not found in sender" so to me it looks like a different issue.
Oh well... Nothing like a bit of fun.

Analyzer Report Group Log

I am trying to find out whether it's possible to log which Report Group the users are using automatically. The Administrator Console can be used to get the trace, but I have to check the radio button on each user that are currently logged in.Thanks in Advance,Tony

Hi
To create a Transaction Code for a Report Painter/report writer report
Tcode for Report Painter
To create a TCode, follow the steps below.
1) Go to Transaction code SE93, Enter TCode Name and Press Create.
2) Give short Description and select Parameter Transaction, Press Enter
3) Select Transation Radio Button and write START_REPORT in the next text
box Also Check the box Skip Initial Screen.
4) On the bottom of Screen (default Values), Enter Parameters
i) Name = D_SREPOVARI-REPORTTYPE. Value = RW
ii) Name = D_SREPOVARI-REPORT Value = Your Report Group Name (Say 1SIP)
5) Save and Execute.
Reward points for useful Answers
Regards
Anji

Creating Report Group

Hi. I'd like to ask how to create / edit a Report Group? I'd like to create one, put 2 reports there and write transaction which will launch that report group. I'd be thankful for help or links Greetings. P.

Hi,
To Create a Report Group, In SAP Menu Follow the below link.
Information system ® Tools ® Report Painter ® Report Writer ® Report group ® Display/Change/Create/Delete
To create a Transaction Code for a Report Painter/report writer report
Tcode for Report Painter
To create a TCode, follow the steps below.
1) Go to Transaction code SE93, Enter TCode Name and Press Create.
2) Give short Description and select Parameter Transaction, Press Enter
3) Select Transation Radio Button and write START_REPORT in the next text
box Also Check the box Skip Initial Screen.
4) On the bottom of Screen (default Values), Enter Parameters
i) Name = D_SREPOVARI-REPORTTYPE. Value = RW
ii) Name = D_SREPOVARI-REPORT Value = Your Report Group Name (Say 1SIP)
5) Save and Execute.
Regards,
Lijo Joseph

Routing Consistency Check in batch ?

Hey folks!
A business requirement has been raised to perform a consistency check for all Routing Task Lists for a specific plant. I'm aware of the consistency check within the Routing that can be performed online. Anyone know of a batch/background job that can validate routings and report errors?
The business case is as follows: Reference Operation Sets are utilized within Routing Task Lists. If a change is made to the Reference Operation Set (say add additional operations) and these additional operations conflict in the routing this ROS is utilized, this will cause a routing error. Yet there is no way to identify this error until someone checks the routing or writes a production order against.
Any help on the above would be great. Points are waiting to be awarded!

Nathan,
I do not think there is a background program that can run to check for such inconsistency.
However when MRP runs system will detect routing inconsistency & will display exception message against planned order.
So nett result is MRP controller will know about this much before he converts planned order to production order.
They can look for exception messages either under Tcode: MD04/ MD05 or collectively under MD06/MD07 group by exception message.
Message 62 - Scheduling: Master data inconsistent is one such message & it falls under Exception group 4 in standard SAP.
So if MRP controller checks Tcode : MD06 & limits selection criteria by exception group 4 messages he can nail down all such errors in advance.
Thanks,
Ram

LiveCache Consistency Check question, OM17

I have a general question about a LiveCache Consistency Check (transaction OM17). I know that it is a data inconsistency b/w the SAP APO database and SAP APO LiveCache. But what does that mean to a functional user? Can someone explain this in layman's terms?

In Layman terms, you can say that this checks the INCONSISTENCY between LiveCache and Database.
Here is a detailed documentation on each of the Object Types
Consistency Check for Setup Matrices
The consistency check for setup matrices contains:
· A check whether the setup matrices exist in liveCache
· A check whether the setup transitions exist in liveCache
· A field comparison between the setup transitions in the database and those in liveCache
When the setup matrices are corrected, the setup matrices in liveCache are completely generated from those in the database. Previously nonexistent setup matrices and setup transitions are newly created in liveCache. Superfluous setup transitions are deleted from liveCache. Setup transitions that differ at the field level are adjusted to match the database status.
Consistency Comparison for Block Basis Definitions
Use
When you set this indicator, checks are performed in liveCache and in the database on characteristic values for block basis definitions:
· The existence of block basis definitions is checked.
· The consistency of the characteristic values is checked.
After the checks you can call a correction function in the check results display. When correcting the error, the system deletes obsolete block basis definitions in liveCache. The system completes or corrects missing or inconsistent block basis definitions in liveCache.
Note
The check is performed independently of the planning version.
Consistency Check for Resources
The consistency check for resources contains:
· A check that the resource and corresponding time stream exist in liveCache
· An check that a resource's characteristic blocks exist in liveCache
· A field comparison between the database resource and the liveCache resource
When correcting the resources, the resources in liveCache are completely generated from the database resources. Previously nonexistent resources are created in liveCache.
Consistency check for downtimes caused by maintenance order
The consistency check for maintenance downtimes contains:
A check that the maintenance downtime has a reference to an existing maintenance order.
A check that the dates of maintenance downtime correspond to the exisiting maintenance order.
When correcting the maintenance downtime errors, downtimes without maintenance order are deleted and wrong dates of downtimes are corrected in relation to the maintenance order.
Consistency Check for Product Location Combinations
Use
If you set this indicator the system executes a consistency check for product location combinations. The consistency check for product location combinations includes:
· A check for the existence of a product location combination in the database and in liveCache
· A field comparison between product location combinations in the database and in liveCache
· The determination of obsolete entries for product location combinations in the database
· A check for the existence of characteristic value assignments for product location combinations in the database and in liveCache
· A field comparison of characteristic value assignments for product location combinations in the database and in liveCache
After the check you can call a correction function from the display of check results. For the correction, the system deletes obsolete product location combinations from the database and in liveCache. The system corrects inconsistent product location combinations and characteristic value assignments for product location combinations in liveCache.
Consistency Check for Stocks
Use
If you set this indicator the system executes a consistency check for stocks. The consistency check for stocks includes:
· A check for the existence of a stock in the database and in liveCache
· A field comparison between stocks in the database and in liveCache
· The determination of obsolete entries for stocks in the database
· A check for the existence of characteristic value assignments in the database and in liveCache
· A field comparison between characteristic value assignments for batch stocks in the database and in liveCache
After the check, you can call a correction function from the display of check results. For the correction, the system attempts to correct inconsistent stocks in the database and in liveCache. If a correction is not possible, the stocks are deleted in the database and in liveCache. The system corrects characteristic value assignments for batch stocks in liveCache.
After inconsistent stocks have been corrected, it may be necessary to start the delta report in order to reconcile SAP APO and SAP R/3.
Consistency Comparison of Configuration/CDP for Orders
Use
When you set this indicator, the system performs a consistency check with regard to configuration or CDP (characteristic value assignments/ requirements) for receipts/requirements belonging to orders:
· In the case of products with variant configuration and product variants, the system checks whether there is a referenced configuration in the database.
· In the case of products with CDP, the system checks whether CDP characteristics exist.
Note
In the area Restrictions, you can use the indicator CDP: Detailed Check to define a detailed check for CDP characteristics. If you set this indicator, the CDP data used for the orders is also compared with the product master.
· For products without configuration/CDP, the system checks whether invalid references to variant configuration or invalid CDP characteristics data exist.
After the check, you can call a correction function in the check results display. When executing the correction, the system tries to adjust inconsistent orders in liveCache.
After inconsistent orders have been corrected, you may need to start the delta report to compare the SAP R/3 system and SAP APO again.
Dependencies
The consistency check for configuration or CDP data is very time-consuming. You should therefore limit the comparison as far as possible to certain products or locations.
Consistency Check for Production Campaigns
If orders are assigned to production campaigns that do not exist in the database, this leads to inconsistent campaigns.
You can correct inconsistent production campaigns by removing all orders from them. That means that the campaign assignments are removed from the orders in liveCache.
Consistency Check for Operations
In the database table of /SAPAPO/OPR operations, there may exist operations that have no orders in liveCache, no orders for a simulation version, orders for deleted simulation versions, or no external operation number. These operations place an unnecessary load on the database table and can hinder system performance.
Consistency Check for Planning Matrices
As planning matrices are not master data, they are only located in liveCache. For each production version, there is a record in the database with information about matrices that must exist for this production version and whether the last matrix explosion was successful.
The consistency check for planning matrices checks:
· Whether the matrices associated with each record on the database exist in liveCache
· Whether the records associated with all the matrices in liveCache exist on the database
· Whether the last matrix explosion was successful.
If inconsistencies are discovered, they can be corrected. As corrections are made by recalculating the inconsistent matrices, the process can take a while and should only be done for large matrices (with many orders or many item variants) at times when it can be guaranteed not to hinder any other system processes.
Consistency Check for Simulation Versions
This is a check for whether simulation versions exist in liveCache.
Correction does not take place automatically. Simulation versions that still exist in the database but no longer exist in liveCache do not influence the running of the system. If necessary, they can be deleted using transaction /SAPAPO/CDPSS0.
Consistency Check for Product Allocations
The consistency check for product allocations checks the data for product allocation assignment from the database and compares this with the incoming orders quantity in Demand Planning. Surpluses or shortages are displayed and can be corrected.
The reconcile is only executed for product allocation groups with a direct connection to the product allocation group in the planning area if the connection is also fully defined.
There may be long runtimes during the consistency check due to the data structure. The following factors can hinder performance:
· Number of characteristics combinations
· Number of periods in a time series
· Number of sales orders that take product allocations from a time stream
Error in the reconcile
If it is not possible to reconcile the incoming orders quantity, the data records are issued again with a relevant error message. Check the following causes and attempt again.
Check:
· If the planning area to be checked is locked
· If the time streams are initialized (after liveCache has been initialized)
· If all characteristics combinations area available in the planning area
· The wildcard indicator for collective product allocation
· The settings for your planning area
Due Delivery Schedules/Confirmations Consistency Check
When a scheduling agreement release is received from a customer for sales and distribution scheduling agreement items, a due delivery schedule is created and stored in liveCache. As soon as a confirmation for a due delivery schedule containing at least one schedule line with a quantity larger than zero is generated, an object is also created for it in liveCache. The transaction data for sales and distribution scheduling agreement items contains, amongst other things, an entry with the key of the due delivery schedule object currently located in liveCache and an entry with the key of the confirmation that is currently valid in the database. During the check, the system checks whether liveCache objects exist for sales and distribution scheduling agreement items and whether the transaction data entries are correct.
The following individual checks are made for active sales and distribution scheduling agreement items:
· Is there an operative scheduling agreement release and/or forecast/planning delivery schedule in the database, but no associated liveCache object?
· Is there a confirmation in the database, but no associated liveCache object?
· Is there a due delivery schedule in liveCache, without at least one existing operative scheduling agreement release and/or forecast/planning delivery schedule?
· Is there a confirmation in liveCache, without an existing confirmation in the database?
· Is the key in the transaction data in the database that shows the current due delivery schedule in liveCache, also that of the actual liveCache object?
· Is there actually a confirmation in the database for the key in the transaction data that shows the currently valid confirmation in the database?
If a sales and distribution scheduling agreement item is inactive, there are not allowed to be any due delivery schedules or confirmations in liveCache. In this case, the following checks are made:
· Is there a due delivery schedule in liveCache for an inactive sales and distribution scheduling agreement item?
· Is there a confirmation in liveCache for an inactive sales and distribution scheduling agreement item?
Consistency Check for Production Backflushes
Partially confirmed orders cannot be deleted from liveCache. For each partially confirmed order of the database table, there must be a corresponding order in liveCache. If no order exists, there is a data inconsistency that can only be rectified by deleting the order from the database tables of the confirmation.
Entries for orders that have already been confirmed exist in the status matrix. The entry in an order's status matrix is deleted when the confirmed order is deleted by the /SAPAPO/PPC_ORD archiving report. Each status matrix entry for which database tables of the confirmation do not exist, present an inconsistency that can only be removed by deleting the status matrix entry.
Consistency Check for iPPE Objects
The iPPE object is not an iPPE master data structure. It is a data extract that is generated for each iPPE access object.
The consistency check for the object checks that it exists in liveCache and also determines its identity using the backup copy in the database. When correcting the object, the copy from the database is written to liveCache.
It is necessary to check the object if the following error message occurs: 'Error while calling COM routines via application program' (/sapapo/om 102) with return code 1601, 1602, or 1603. This does not apply to liveCache initialization.
Consistency Check for Procurement Scheduling Agreement Items
The following three objects represent procurement scheduling agreement items (scheduling agreement in short):
1. Scheduling agreement schedule lines
2. Release schedule lines
3. Confirmations
All these objects are located in liveCache. Release schedule lines and confirmations are also located in the database with a historical record. Depending on the process that was set up for the scheduling agreement, not all objects exist in liveCache or have historical records.
If goods movements exist for an object, there must always be at least one entry in liveCache. If all schedule lines are covered by goods receipts, at least one schedule line will exist in liveCache with the number '0000000000' and an open quantity of 0.
A liveCache crash, operator errors, and program errors can all cause inconsistencies. Below is a list of all the inconsistent statuses that have been identified and that can be removed:
1. The object is not in liveCache but goods receipts exist.
2. The number of input nodes and output nodes is different.
3. There are no input nodes at the order, but the material exists in the source location for the order.
4. The original quantity at the source of an order is different from that at the destination.
5. The accumulated quantities in liveCache are different from those in the database (the cumulative received quantity, for example).
6. The set process is compared with the status in liveCache.
7. A check is made to see whether the scheduling agreement is being planned in APO or in R/3 and whether the schedule lines have the appropriate specification.
If a schedule line inconsistency is identified, no more checks for inconsistencies are made, instead it moves on to the next schedule line.
Consistency Check for MSP Orders
Provides a list of maintenance and slot orders that
·     Exist in the database but have no corresponding orders in the liveCache
·     Exist in the liveCache, but have no corresponding orders in the database
Procedure
From within the list, you can either
·     Correct the inconsistencies
If you choose to do this, the system deletes the selected orders from the database and/or liveCache.
You receive a message that the selected order(s) have been deleted.
·     Leave the inconsistencies in the database and/or liveCache
Such inconsistencies place an unnecessary load on the database and/or liveCache. Moreover, those orders that exist in the liveCache, but have no corresponding orders in the database, influence the scheduling results of subsequent orders in the liveCache
Hope this helps
Regards
Kumar Ayyagari

The time characteristic consistency check has produced an error DBMAN 62

Hi
We are getting an error while updating to one target as The time characteristic consistency check has produced an error""
* Checked the respective PSA data field which is fine. Dates are in correct format.
* RSRV ran for the particular target. It had error but the jobs were successful till yesterday.
* Data from 01.05.2014 is having the problem ( Which I got from the record number in PSA )
NB: We are running on HANA database but the respective target is not yet HANA Optimised
Details Figures Attached
Any Idea.. What could have gone wrong
Regards
Reshoi R

Hi
Record Number 2995 is shown in the figures attached.
I have already carried out the deletion and automatic repair mentioned in RSCV061 even before posting this question but of no use ( I have shown that also in the figures attached at the posting time.
Reporting is fine. The problem is while loading the data to the cube. The loading is fine till date 30.04.2014 but from the date 01.05.2014. The record is error while updating.
The cube is partitioned from month 01.2008 to 12.2015.
Regards
Reshoi R

REPORT GROUP tcode: gr52

I have created a custom program and added it to a standard report group in GR52. But when i execute the Main Report group and try to drill down to the custom transaction code. The sy-tcode is still START_REPORT. Is there a setting i am missing when creating the custom report transaction. While creating the transaction i selected it as a regular report transaction.
thanks
Kshamatha

YOu have to create a "Parameter Transaction"
For "Defualt values" tab,
transaction - START_REPORT
Check the "Skip initial screen"
Press one ENTER here.
GUI support - all 3 checkboxes
Default values (table control at last) .. you can use F4 here for the field optoins on the screen field name
Screen field name
D_SREPOVARI-REPORTTYPE RW " < you report group
D_SREPOVARI-REPORT 5A21 " < report
Save and activate.
Regards
Naimesh Patel

Consistency check error in OBIEE 10g

Hi
I have the below error while doing consistency check.
I was trying to join two fact tables by complex join, but getting below error
NQSError:15009 Could not load navigate space for subject area
NQSError: 15009 Multiple paths exist to table Plans.Circular joins schemas not supported
Please suggest

If you have to join fact tables in physical, make sure your logical layer remains a star.
Either add both fact tables to one logical fact table source , or create two logical stars, where both facts are joined to all conformed dimensions.
Note: if both facts are not at exactly same granularity, your reports will show incorrect results most definitely. So avoid fact to fact joins.

Report painter:Deletion of multiple report groups

Hi Gurus,
I have a requirement of deleting multiple report groups and reports created through report painter since these are no more used
I checked in options/functions available in SAP, but couldn't find any option for mass deletion of reports groups available
I understand we can use an LSMW to do this for multiple report groups however apart from this is there any function provided by SAP for deleting multiple report groups
Thanks,
Gaurav

Hi Ajay,
Thanks for the suggestion
I also couldn't find anything handy. In my case the time in manually deleting would have taken less than creating an LSMW for such one-off situation so just delete the obsolete report groups manually
Thank you,
Gaurav

Errors occur during executing consistency checks

Hi all,
During my phase"executing consistency checks", errors occur :
X_STXH| Sender structure S_STXB is not assigned to the receiver structure R_STXB.
It happened in PC001_PCL_CHECK sub-activity.
The details as follows:
ubactivity PC001_PCL_CHECK was started on 08.03.2009 at 22:10:02 by user LEEE03 | |
Check COBJ started at 08.03.2009 22:10:30 by LEEE03
Check COBJ finished at 08.03.2009 22:11:04 by LEEE03
Check HIER started at 08.03.2009 22:11:04 by LEEE03
Check HIER finished at 08.03.2009 22:11:04 by LEEE03
Check RELS started at 08.03.2009 22:11:04 by LEEE03
X_STXH
Sender structure S_STXB is not assigned to the receiver structure R_STXB
X_STXH
Sender structure S_STXB is not assigned to the receiver structure R_STXB
X_STXH
Sender structure S_STXB is not assigned to the receiver structure R_STXB
X_STXH
Sender structure S_STXL is not assigned to the receiver structure R_STXL
X_STXH
Sender structure S_STXL is not assigned to the receiver structure R_STXL
X_STXH
Sender structure S_STXL is not assigned to the receiver structure R_STXL
Check RELS finished at 08.03.2009 22:11:20 by LEEE03
Check RULE started at 08.03.2009 22:11:20 by LEEE03
Check RULE finished at 08.03.2009 22:11:29 by LEEE03
Check DICT started at 08.03.2009 22:11:29 by LEEE03
X_STXH
Field TDNAME does not exist in the sender structure on sender system
X_STXH
Field TDOBJECT does not exist in the sender structure on sender system
X_STXH
Field TDID does not exist in the sender structure on sender system
X_STXH
Field TDNAME does not exist in the sender structure on sender system
X_STXH
Field TDOBJECT does not exist in the sender structure on sender system
X_STXH
Field TDID does not exist in the sender structure on sender system
Check DICT finished at 08.03.2009 22:11:29 by LEEE03
Check FIMA started at 08.03.2009 22:11:29 by LEEE03
Check FIMA finished at 08.03.2009 22:11:31 by LEEE03
Check RUMA started at 08.03.2009 22:11:31 by LEEE03
Check RUMA finished at 08.03.2009 22:11:31 by LEEE03
Check SELS started at 08.03.2009 22:11:31 by LEEE03
Check SELS finished at 08.03.2009 22:11:33 by LEEE03
Subactivity PC001_PCL_CHECK was completed on 08.03.2009 at 23:11:40 with status ERR
I have searched in sap marketplace and also google, no results come out.
Could anybody help me out?
Thanks.
Best Regards,
Eric Lee

I've implemented the note 1101544 in the central system
executed the report Z_CNVTDMS_08_FIELD_SET with P_PHASE to 'S'.
and after this, I re-executed the activity "Execute Consistency Checks" from the extended mode of the process tree several times.
But it remains the same issue.
Did I miss anything?

To add new characterstics to a report group

Hi,
We have created a report group under 601 library. Structure used is CCSS. But we need the field currency type to be added as a characterstic. Since it is not avialable in CCSS we are unable to do that.Please suggest a way.
Thanks,
Seema.

Hi Shamia,
Check these Tcode for Report painter,
Report painter....
GRR1, grr2, grr3
GS11, 12, 13 for variable
GS01, 01, 03 for sets
GR51, 52, 53 for report group
GR21, 22, 23 for library
for export-import:
-Any new variables (GS17 - Export ,GS18 - Import )
-new sets (GS07 - Export ,GS08 - Import )
-new report (GR37 - Export ,GR38 - Import )
-new report group (GR57 - Export , GR58 - Import )
-new library (GR27 - Export , GR28 - Import )
[Report Painter|http://www.virtuosollc.com/PDF/Get_Reporter.pdf]
Hope your problem solves.
Thanks & regards,
Dileep .C

Transaction code creation for a report group

Hi all,
I created a transaction code ZF17 for a report group FI02 with the following parametrs.
Transaction: START_REPORT
checked the skip initial screen check box.
D_SREPOVARI-REPORTTYPE = RW
D_SREPOVARI-REPORT = FI02
When i tried to run the T-code ZF17, it gives me
a message : PROGRAM FI02 doesn't exist
Any ideas why this message comes up?
Thanks,
Sobhan.

I would think that its looking for a program name in the D_SREPOVARI-REPORT field, FI02 is not a program name.
Regards,
Rich Heilman

Report Group 1SIP Consistency Check

Similar Messages

Maybe you are looking for