Generation Log

Hi Experts,
I have doubt regarding the Generation log which is generated in R/3 system. Can any one please give significance of generation log?
Thanks in advance,
Chandu.

Hi......
The generation log provides an overview of the individual actions that would be performed in the real creation mode........
Check this.....
Generation Log for Trasfer Structure on Source System
http://help.sap.com/saphelp_nw04/helpdata/en/cf/f24a4259b4be30e10000000a155106/frameset.htm
Regards,
Debjani.....

Similar Messages

Generation Log for Trasfer Structure on Source System

Hey Folks, I'm reciving a weird message at the moment of activate the transfer rules, something like:
Error when creating transfer structure /BIC/CCGO0CO_PC_01 in source system XXXX,An error occurred when creating transfer structure /BIC/CCGO0CO_PC_01 as an IDoc segment in source system XXXX Meesage Number : R3104
Could someone explain where on the source system Side can I check the generation log for this?
Thanks a lot

Hi William,
The problem may be because of some error in connection with Source System . Check all entries in table T000. Note them up in field RLOGSYS and check with RSBASIDOC with fields Rlogsys and Slogsys .
U can see the Source System assignment and IDoc type is the table RSBASIDOC .
Check the field RlOGSYS in the table.The possible cause of error is caused because of renaming the Source System
Check with the assignment in Sourcesystems of BW .
also Check with Transaction RS_LOGSYS_CHECK in R/3 .
U can have more information in the OSS Notes : 140276
Hope it helps.
Thanks,
krish
*Awarding points is a way of saying thanks in SDN
Message was edited by: krishna V

MW generation error for SRV_WRITE after Upgrade to CRM 7.0

Iu2019m finishing up with the post-processing steps for the CRM 7.0 upgrade of our development system (from CRM 2007) and ran into an issue when re-generated the Middleware services before activating the MW.
Per the upgrade guide, I ran GN_START to start the generation, but the results in GENSTATUS show the below 8 errors. These errors are preventing me from activating MW, regardless of whether weu2019re actually using these services or not. I ran into this same issue in our Sandbox for the SRV_WRITE object and managed to resolve it there by generating some specific objects using the Generation Workbench (GNRWB), however the same approach has not worked for our Dev system. We have NOT implemented the Mobile CRM scenario, but are replicating BPs and Material with R/3, and have begun configuring the Server-based Groupware Integration which uses the Middleware framework and CDB.
/1CRMGC/SRV_WRITE_DEL:The data object "<FS_AFTERCDB0003>" does not have a component called "UPDATE_FLAG".
Could not determine module name: SRV_WRITE GENKEY: EXTRACT
Could not determine module name: SRV_WRITE GENKEY: REALIGN_GET_DEP_INT_OBJ<IND>
From what I can tell, SRV_WRITE is used somehow with Service Order replication?
Any suggestions for next steps to resolve these errors? Thanks for any input anyone can offer.

Thank you for the post. After comparison of Dev system with Sandbox, I think I am missing FM /1CRMGC/HTSRV_WRITE_RRX in Dev. However, when I try to generate in GNRWB using the below parameters, I am getting the errors below. How to proceed? Once again, thank you for your help!
GNRWB Generation:
Gen Group = RRLEX: Replication Extract
Industry = High tech
Rep Object = SRV_WRITE
Generator = EXTRACTWR
Generation Log:
No runtime object for generator REPLI_FLOW_FUGR and object SRV_WRITE registered in TGN_OBJREG
No runtime object for generator REPLI_FLOW_FUGR and object SRV_WRITE registered in TGN_OBJREG
thanks,
John

BW3.5: Error message when trying to activate the transfer rule

When I was trying to activate the transfer rule for one info object( charateristic with master data) , I got the following error in [[ ]]
Error when creating transfer structure /BIC/CCPIZGR00CC_ATTR in source system CI2220
Diagnosis
An error occurred when creating transfer structure /BIC/CCPIZGR00CC_ATTR as an IDoc segment in source system CI2220 .
System response
The action was terminated. No data was changed.
Procedure
Use the generation log in source system CI2220 to identify the error, and remove the cause.
CI2220 is the backend R/3 system, I had no issue in replicating the data source etc. this error occurred while trying to activate the transfer rule after assigning the info source to the replicated datasource in BW.
Can anybody tell me how to view( what transaction etc) the generation log to understand the issue?
Thanks in advance
Arunabha

Hi Roberto,
Thanks for yoyur prompt reply, I would try to follow the instruction, but at the same time please note that previously we had no issue in activating the transfer structure. I would like to see the log in the source system, but don't know how to and which transaction to use etc. any help would be appreciated.
Thanks
ARUN

Transfer Structure Error

Hi Guys,
I am getting the following error when trying to activate Transfer Structure for 0PLANT_TEXT in BW.
Error when creating transfer structure /BIC/CCGB0PLANT_TEXT in source system ORAGDV130
Message no. R3104
Diagnosis
An error occurred when creating transfer structure /BIC/CCGB0PLANT_TEXT as an IDoc segment in source system ORAGDV130 .
System response
The action was terminated. No data was changed.
Procedure
Use the generation log in source system ORAGDV130 to identify the error, and remove the cause.
I am using PSA as the transfer method. Any help is appreciated.
Thanks.

Hi Govind,
To implement what is said in the note IS VERY EASY!
I have even created this program in my system. It seems to be very very useful program. Not only for your case. THE PROGRAM CHECKS CONSISTENCIES IN THE SOURCE SYSTEM AND CORRECT THEM! It may help in many problems with source systems.
So, here is a way to implement the program.
- In the text tabstrip of the note click on 'Correction Instructions' tabstrip.
- Then in the 'Ref. Correction' column choose a number that corresponds to your system PI (click on it).
- Click on a report name 'z_rs_scrsystem_r3_check'.
- In your BW system execute tcode SE38 (or ask someone with a development key), give the name 'z_rs_scrsystem_r3_check', click on a button 'create'.
- Enter program description, choose 'executable' option.
- Into the screen of ABAP Editor copy-paste the code from the note correction instructions.
- Click on 'Check', then 'Activate' icons.
- If everything is OK, press F8 (execute).
Then follow the note:
"These programs have the following input parameters:
SLOGSYS Specify the logical system name of your source system here
RLOGSYS Specify the logical system name of the BW system here
If you enter nothing here, all existing BW source system connections are processed.
Use the NO_DB_UP parameter to control whether the program works in check or correction mode. The NO_DB_UP = 'X' default represents check mode.
2. First execute the Z_RS_SCRSYSTEM_R3_CHECK program in check mode. The inconsistencies detected by the program are issued as a log. Now start the programs in correction mode (NO_DB_UP = ' '). Then execute the program again in check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run. Then execute the program again in the check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run.
3. If the error continues to occur:
Check the transfer structure in the source system using transaction SE11. Use note 147195 if namespace conflicts are reported in the consistency log.
After the correction has been made, you should check to see whether it is possible to switch your transfer rules from the IDoc transfer method to the PSA transfer method.
We recommend that you use the PSA transfer method."
Best regards,
Eugene
Message was edited by: Eugene Khusainov

Standard Sales Analsis Report with Customer Name and Location

Hi All,
Can Anybody provide a custom query for the standard slaes Analysis report which includes Customer Name , Location columns in the Standerd Report.
Regards,
srini

Hi nick,
See if anybody has worked on SIS (sales information system) in your team.
He can help you out to create one info structure , by selecting desired characteristics, key figure with respective update rules. though its require lot of configuration but you can make it without abap development.
(I couldn"t make it in time to provide you detailed configuration but below given path will take you to the configuration area )
IMG - LG -Logistick information system -logistick data werhouse- data basis- field catalogue.
IMG - LG -Logistick information system -logistick data werhouse- data basis -
infostructure.
IMG - LG -Logistick information system -logistick data werhouse- data basis - updating - update defination & update rules.
( MC18, MC21, MC24,& MC30)this transaction help to create field catelogue, info system, update rule & generation log respectively.
karnesh

Impact of Analysis Authorization on Users using old Authorization

Hi All,
I have question regarding Analysis Authorization. Our system has old authorization concept and as part of our project we decided to go for Analysis authorization for Cost Center object. We activated analysis authorization for cost center, assigned it to test user id and found that its working fine in Dev. But it has impacted other users in the system. They are not able to access any other reports and data providers which were not even referring cost center. What is the proper way to activate analysis authorization without impacting access to existing users.
- Som

Hello Andreas,
Sorry to ask you directly here, I didn't get answer from this forum. We will migrate to the new analysis authorization from old reporting concept. I have read the book "An Expert guide to new SAP BI security features" by SAP Lavs, but still confused with some parts. My questions is:
Are there two ways to create authorizations as follows?
1. we can type tcode rsecadmin>Maintence button>create a new authorization.
2. the following part taken from the book:
Steps for Generating Authorizations
1. Activate Business content
2. Load Datastore objects
3. Generate Authorizations
4. View Generation Log.
In the first step, OTCA_DS01 to OTCA_DS05 and OCCA_O01 to OCCA_O03 are Datastore objects required to be activated.
In the second step, tcode rsecadmin-->generation button --> type OTCA_SDS01 to OTCA_DS05 into respective filed. Should we always type these 5 objects everytime when we create authorization?
When we should use the second way to create authorizations? and what is the diffrence between them?
Any answers will be appreciated. Thank you very much in advance!
Haifeng

Error while activating the infoprovider 0PS_C04 from BI content

Hi,
We are trying to activate Infoprovider 0PS_C04 from BI content and getting following error. We have applied OSS Note 493422 and also tried several options by granting appropriate authorizations to the RFC user BID_CUA_200 being used for the extractors. However, we are still getting following error message. Unfortunately we have been experiencing this problem for most of the Infoobjects
Kindly throw some light on this please. I will certainly reward full points.
Best Regards
Venkat. P
"Error when creating transfer structure /BIC/CCBA0CURTYPE_TEXT in source system ECDCLNT200
Message no. R3104
Diagnosis
An error occurred when creating transfer structure /BIC/CCBA0CURTYPE_TEXT as an IDoc segment in source system ECDCLNT200 .
System Response
The action was terminated. No data was changed.
Procedure
Use the generation log in source system ECDCLNT200 to identify the error, and remove the cause.

And also check whether there are any dumps in ST22.
Khaja

Problem with Billing Engine after upgrade from CRM 5.0 to CRM 7.0

Hello together,
The system of our customer has been upgraded from CRM 5.0 to CRM 7.0. After that some problems occurred regarded the billing.
In the Billing Due List a dump occurs when clicking on an item and then on conditions
Dump message: No function module can be found named "/1BEA/CRMB_DL_PAR_O_DERIVE" however.
(Other classes are new generated after the upgrade)
During the Analysis we looked to the billing engine navigator:
In the Billing Engine Navigator (Transaction: BEFN_F1) the Generation Log shows the following:
We have re-generated the Object PAR in CRMB->DL->Feature->PAR. But this shows the above displayed error message. How can we add value to the Placeholder?
Another question is which impacts does it have if we regenerate the complete billing engine for CRMB with transaction BEA_CONFIG_F1 (Configure Application)?
BR, Anne

Hi Nawanit,
we checked the key figure settings and categories. Everything is maintained correctly.
Since we work with MRP areas we also checked the "Global Parameters and Default Values for MRP Areas" in APO Customizing: The "Default values for Stock Transfer Documents" is set to "1" = Stock Transport Requisitions for MRP Areas.
BUT: When I try ot change this indicator I get the following message no. /SAPAPO/MRPA000:
"Process. w. stock transp. requisitions is not supported in standard sys. The process with stock transport requisitions will be supported as of SAP R/3 Enterprise Core Release 4.70 with SAP R/3 Enterprise Extension Set 2.0. ".
As far as we work with ECC 6.0, EHP4 this message makes no sense.
Does anyone have another idea?
Thanks
Jan

Report with customer info for an Sales Order with batch details

Hi
Can any one please tell me the SAP REPORT with contains data of customers were shipped a specific product (material number) by batch number. report with the name and address of the customer, the sales order number and the number of products that were shipped.
Thanks
Nick

Hi nick,
See if anybody has worked on SIS (sales information system) in your team.
He can help you out to create one info structure , by selecting desired characteristics, key figure with respective update rules. though its require lot of configuration but you can make it without abap development.
(I couldn"t make it in time to provide you detailed configuration but below given path will take you to the configuration area )
IMG - LG -Logistick information system -logistick data werhouse- data basis- field catalogue.
IMG - LG -Logistick information system -logistick data werhouse- data basis -
infostructure.
IMG - LG -Logistick information system -logistick data werhouse- data basis - updating - update defination & update rules.
( MC18, MC21, MC24,& MC30)this transaction help to create field catelogue, info system, update rule & generation log respectively.
karnesh

Backup size is increased after resync catalog

Hi everyone,
I have describe my problem, if anyone have a solution please provide me.
Rman catalog database version : 10.2.0.1.0, OS : red hat linux
Target database version : 10.2.0.5.0, OS : solaris 10
rman catalog database space is full, then i move my example tablespace to another location, but i forgot to change the ownership of new file.
And I have no backup of my rman catalog database. so i offline the datafile first for opening the rman catalog database after opening the database I have offline the whole example tablespace and this tablespace cannot contain any thing related the catalog.
after that I used the command : crosscheck archivelog all;
DELETE EXPIRED ARCHIVELOG ALL
then i run the command : CROSSCHECK BACKUP;
DELETE EXPIRED BACKUP;
then i run the command : report obsolete;
delete obsolete;
then i run the command : RESYNC CATALOG;
then i run the command : change archivelog all validate;
after doing all the thing when I am taking a backup of archive log by using following command :
run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/ARCH_%d_%s.bak';
backup archivelog all;
before performing all the above thing my archive backup of whole day is around 5gb but after the above thing my archive backup of one day is around : 126gb
and my level0 backup is alright after and before the above thing and the size is around : 139gb
the script for the full backup is :
run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/FULL_%d_%s_%c.bak';
backup incremental level 0 database skip offline;
after that I have perform the incremental level 1 backup by using the following script :
run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/INC1_%d_%s_%c.bak';
backup incremental level 1 database;
before the above activity the size of incremental backup is around : 4.5gb but after performing the above activity the incremental backup size is around : 120gb
it is very critical for me, if any one have the solution please provide me as early as possible.
Thanks & Regards
Rakesh Kumar

Hi Hemant K Chitale,
you said that I am using the COMPRESSED BACKUPSETs till 22-Jan, so I am posting
the rman configuration here that is used before all this happening and same
configuration is used right now.
but before resync catalog the archivelog is generated only one location then I used to archive log
dest for archive log generation then after 5 month I will resync my catalog. may be it is the
reason.
because there are no compressed backupset is defined in the rman configuration.
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/appl2/prodback_rman/prod_fullbackup/ctrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/appl2/prodback_rman/prod_fullbackup/prod_%d_%s_%c.bak', '/appl2/prodback_rman/usb/prod_%d_%s_%c.bak';
CONFIGURE MAXSETSIZE TO 20 G;
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/appl2/prodback_rman/prod_fullbackup/snapcf_PROD.f';
Archive log generation log on the daily basis.
SQL> select trunc(COMPLETION_TIME,'DD') Day, thread#,
round(sum(BLOCKS*BLOCK_SIZE)/1048576) MB,
count(*) Archives_Generated from v$archived_log
group by trunc(COMPLETION_TIME,'DD'),thread# order by 1;
DAY THREAD# MB ARCHIVES_GENERATED
04-FEB-13 1 2776 37
05-FEB-13 1 16767 220
06-FEB-13 1 16545 216
07-FEB-13 1 15772 208
08-FEB-13 1 15056 198
09-FEB-13 1 18486 244
10-FEB-13 1 17591 232
11-FEB-13 1 18163 238
12-FEB-13 1 15062 198
13-FEB-13 1 26383 342
14-FEB-13 1 36279 462
DAY THREAD# MB ARCHIVES_GENERATED
15-FEB-13 1 34010 432
16-FEB-13 1 32230 413
17-FEB-13 1 31904 408
18-FEB-13 1 33448 426
19-FEB-13 1 34639 444
20-FEB-13 1 36684 468
21-FEB-13 1 27547 352
right know the archive log backup size by rman is around 19gb per day.
so tell me how we reduce the size of my archive log backup according to
my rman configuration and how can i reduce the archive log generation on
my production server on daily basis.
Thanks & Regards
Rakesh Kumar

Read Mode of a Query

Hi All,
what is a Query Read Mode or Read Mode of a Query? why it is used and is it have any Seperate
Transaction code? How to check the Read mode of a Query? what is the use of it?
Thanking

Hi Nagar,
On the Query Properties dialog box for the query monitor you can make settings for a BW query with regard to the read mode. You can switch off the default Parallel Processing for queries on a MultiProvider. For queries with virtual characteristics or key figures you are able to activate the use of the cache, which is deactivated by default. If you activate the display of the generation log you are able to display a log in which you can see the reasons why the query in question was generated again. You do this afterwards using the generation log pushbutton.
USE
The read mode determines how the OLAP processor gets data during navigation. You can set the mode in Customizing for an InfoProvider and in the Query Monitor for a query.
u can get the info
[http://help.sap.com/saphelp_nw04/helpdata/en/57/b10022e849774f9961aa179e8763b6/frameset.htm]
Regards,
NR

SHIPPING EXECUTION에 대해 DEBUG FILE을 생성하는 방법

제품: Applications
작성날짜 : 2006-05-30
SHIPPING EXECUTION에 대해 DEBUG FILE을 생성하는 방법
==========================================
PURPOSE
Shipping Execution에 대해 Debug file을 생성하는 방법을 기술함.
Explanation
Log file을 생성하기 위한 여러 방법들이 있으며, 이는 다음과 같은 patch level에 의해 결정된다.
A. debug file from the Shipping Transaction or Quick Ship forms in
version 11.5.9 or higher.
B. debug file for Pick Release in version 11.5.9 (Family pack I)
or higher.
C. debug file for Pick Release prior to version 11.5.9
D. debug file for Interface Trip Stop - SRS in version 11.5.9
(Family pack I) or higher.
E. debug file for Interface Trip Stop - SRS prior to version
11.5.9 (Family pack I).
F. debug file for an API in version 11.5.9 (Family pack I) or higher:
G. debug file for an API prior version 11.5.9 (Family pack I):
A. To generate a debug file from the Shipping Transaction or
Quick Ship forms in version 11.5.9 (Family pack I) or higher:
1. Set the following profile options:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
WSH: Debug Level - set to Statement
WSH: Debug Log Directory - any directory that can be written to by
the database
여기서, 설정하는 directory는 다음을 check하여야 합니다.
To check, run the following SQL statement:
Code:
select value from v$parameter
where name = 'utl_file_dir'
Set profile option WSH: Debug Log Directory at the Site
& Application Level.
2. Shipping form --> Tools
Debug box를 check. ==> This will print out a file name
- NOTE down this file name.
3. Perform the action you wish to debug.
4. Tools --> uncheck Debug box.
5. After you have completed generating the debug file,
set profile OM: Debug Level back to 0
WSH: Debug Enabled set to No
6. step 1의 debug directory밑에 debug file이 생성됨.
B. To generate debug information for Pick Release in version 11.5.9 or
higher:
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
WSH: Debug Enabled - set to Yes
WSH: Debug Level - set to Statement
2. Release Sales Order for Picking form --> Tools
==>check the Debug box.
3. Submit the pick release.
4. Provide "Pick Selection List Generation" log file.
C. To generate debug for Pick Release prior to version 11.5.9 :
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
2. Release Sales Order for Picking form --> Tools
==>check the Debug box.
3. Submit the pick release.
4. Provide "Pick Selection List Generation" log file.
D. To generate debug for Interface Trip Stop - SRS in 11.5.9 or higher:
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
WSH: Debug Enabled - set to Yes
WSH: Debug Level - set to Statement
Set the Debug Level parameter to 1 (Debugging ON) .
2. Submit the job.
3. Provide the log file.
E. To generate debug for Interface Trip Stop - SRS prior to 11.5.9:
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
Set the Debug Level parameter to 1 (Debugging ON) .
2. Submit the job.
3. Provide the log file.
F. To generate debug for an API in 11.5.9 or higher:
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
WSH: Debug Enabled - set to Yes
WSH: Debug Level - set to Statement
WSH: Debug Log Directory - set to a valid writeable directory path
2. Add the following line of code in the wrapper script which calls
the API:
Code:
DECLARE
l_file_name VARCHAR2(32767);
l_return_status VARCHAR2(32767);
l_msg_data VARCHAR2(32767);
l_msg_count NUMBER;
BEGIN
fnd_profile.put('WSH_DEBUG_MODULE','%');
fnd_profile.put('WSH_DEBUG_LEVEL',WSH_DEBUG_SV.C_STMT_LEVEL);
wsh_debug_sv.start_debugger
(l_file_name,l_return_status,l_msg_data,l_msg_count);
3. Submit the job.
4. Provide the log file.
G. To generate debug for an API prior to 11.5.9 (Family pack I):
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
2. Add the following line of code in the wrapper script which calls
the API:
Code:
oe_debug_pub.initialize;
oe_debug_pub.SetDebugLevel(5);
DBMS_OUTPUT.PUT_LINE('Debug File = '
||OE_DEBUG_PUB.G_DIR||'/'||OE_DEBUG_PUB.G_FILE);
3. Submit the job.
4. Provide the log file.
Example
Reference Documents
Note#290432.1

Invoice Report Error

Hi All,
I got the invoice report in vf05n. But in that report I am getting the sold - to-party number only not the name of the sold-to-party.But my client want the sold-to-party name should come.How to get this.
Its urgent.
Reward points for helpful answer.
Regards
Ashis

hi
better option goto LIS report
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
Change Source information for following to MCVBRP-AUBEL and MCVBRP-AUPOS:
o     Sales
o     Gross Invoiced Sales
o     Net Invoiced Sls 1
o     Net Invoiced Sls 2
o     Inv freight Chrgs
o     Bill Docmnt PS5
o     Bill Docmnt PS6
o     Invoiced Qty
o     Invoiced sls cost
Change Source information for following to MCLIPS-VGBEL and MCLIPS-VGPOS:
o     Open Orders
o     Open Order Qty
- Save and Generate by clicking on the Generate icon.
     Similarly, copy update rules for Update Group 2. Transaction Code MC24.
Repeat these rules for the combination of information structure S990 and update group 2. (Copy from info structure S001 and Update group 2).
Figure 17: Maintain Update Rules for Structure S990 and Update Group 2
Again, click on Rules for charact and verify source information for every key figure, by clicking on previous key figure and next key figure.
Change Source information for following to MCVBRP-AUBEL and MCVBRP-AUPOS:
o     Credit Memos
o     Gross Credit Memos
o     Net Credit Memos 1
o     Net Credit Memos 2
o     Credit memos freight
o     Credit memos subtotal 5
o     Credit memos subtotal 6
o     Credit memos qty
o     Credit memos cost
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 SIS Update
     Lastly, Activate SIS 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 SIS structure S990 with period as Month and update option of Asynchronous Updating (2).
Figure 33: Activate SIS Update for S990
SIS tests with Sales Order Processing (Order>Delivery>Invoice)
     Create a Sales Order, transaction code VA01
Figure 34: Create a standard Sales Order and Sales Order 6437 is saved
(Pricing details)
Figure 35: Pricing Details for the Sales Order
     Execute transaction MC30 to find out which information structures are updated. Please note that this step is not mandatory.
Transaction code MC30 is worth mentioning here. This transaction code, provided user parameter MCL is set to X in users master record, provides analysis of which structures are updated for the activity. It generates a log of updates to Information Structures and detailed analysis. Since, it can take resources, it is advisable not to set user parameter MCL in productive system.
Figure 36: Transaction MC30 lists that Structure S990 is updated
Double-click on S990 line to view more details.
Figure 37: Transaction MC30 details for Structure S990
     Execute Standard Analysis Report.
SAP>Logistics>Sales & Distribution>Sales Information System>Standard Analyses>Self defined analysis (transaction code MCSI). (Choose Structure S990). Enter appropriate values and execute.
Figure 38: Standard Analysis report for Structure S990
Figure 39: Standard Analysis report for Structure S990 for given criteria
     Create a Delivery/PGI and review its impact on Standard Analysis Report.
Delivery 80007493 Saved, execute MC30 to review the update log.
Figure 40: At the time of Delivery/PGI, Structure S990 is updated
Figure 41: At the time of delivery, since Order is no more open, Open Order value is reduced
Please note in the Standard Analysis report that the Open Order value is reduced accordingly.
Figure 42: Standard Analysis report reflects correct Open Order value
     Create an Invoice and review SIS report.
Invoice 90021696 saved. Review Update log with MC30.
Figure 43: Invoiced/Sales amount is updated at the time of invoice
Note that in the Standard Analysis report, Sales value has increased.
Figure 44: Standard Analysis report reflects correct Sales Amount
     Summary changes in Information structure depending upon Sales activity
Sales Order: Note Open Order has EUR 49.60 value.
Delivery: Note Open Order value is reduced.
Invoice: Note Sales column reflects correct invoiced amount.
Figure 45: Summary Information Structures reflects correct values depending upon the status of transaction: whether order created, shipped or invoiced
if u r not understand send me test mail [email protected]
regards
krishna

Integration Builder Configuration. SRM/EBP ---- XI ------ SRM/SUS

Hi Masters of SRM.
could you please show how make the configuration in XI into Builder configurations
the scenario is SRM/ebp -
> XI -
> SRM/SUS
any guide because I have the guide for the ERP----> XI -
>SUS. but does not my requirement.
the both systems are in same box but different client.
thanks for yours atentions

Thanks: Nichil.
I follow your instructions., when I make simulation in Generation Log. show all lights in yellow color for example:
Receiver Determination(s):
| SRD_009 | PurchaseOrderRequest_Out | * | *
Analysis
Required sender communication component: | SRD_009 A receiver determination was found for the connection All receivers are contained in the receiver determination found
Results
The reused receiver determination is already assigned to the configuration scenario
Notes
Check the conditions for all receivers of the receiver determination. The default result value for the generated condition is: TRUE
I am message for test and I can see the message into PI the estatus is Recorded and flag is color Green.
but no show an error or problems only stay in Recorded Status , othe observation into the SXMB_MONI the fiel Receiver component and Receiver Interface are empty,
what you suggets ?
best regards.

Generation Log

Similar Messages

Maybe you are looking for