Details of Follow-up documents at Table level

Dear All,
I want to know if there is any table(s) which contains the follow-up documents numbers that gets generated in CRM.
For example,
1. first IC ticket will be generated,
2. then product complaint will be generated as a follow up transaction of IC ticket.
3. Compensation request transaction will be generated as a follow up of product complaint.
I am already able to get this follow up using BAPI but I want to know how to get this at Database level so as to make report to perform faster.
regards,
Amey Mogare

Hi Amey,
one possibility is to read doc flow using FM 'CRM_DOC_FLOW_READ_DB'.
If you really want to use the tables, here's the description:
1. Table 'SRRELROLES' with OBJKEY = GUID of order --> get the ROLE_ID
2. With ROLE_ID go to table 'CRMD_BINREL' field ROLE_A / B (depends on predecessor / successor)
3. With the other role ( ROLE_A / B) you can go back to table 'SRRELROLES' and get the GUID by the OBJKEY.
Hope, this is useful.
Best regards,
Claudia

Similar Messages

Follow on Document details not correct

Hello Experts,
We are in SRM 4.0 Classic
One Shopping Cart has been created with 1Goods and 7 Service line items....
PR has been created in backend...... (we see generally SC line item 1,2,3.... follow sequece 10,20,30 in PR, But here this order is shuffled.... though all the SC and PR line item details are correct)
Now for SC line item 2, 'follow on document' tab shows details of PR line item 40 and vice versa.... which is incorrect....
Except these two SC line items, all other SC items shows correct PR line item details in follow on document
Can anyone advise on such system behaviour? Is thr any way to fix this?
Thanks,
Dhananjay

Hi,
Did you delete some line items and again added them in your SC? Are you using cost distribution in your SC?
Regards,
Nikhil

Follow on document details not updating in shopping cart

Hi Experts,
I created a shopping cart and created PO as a follow on document from sourcing cockpit after assigning vendor.
but Shopping cart is not updating with follow on document (PO)details even after running BBP_GET_STATUS_2 report also.
Is there any other settings required to do for updating shopping cart with follow on document details.
Thanks,
Bhaskar.

Hi ,
Please check the repots ( jobs ) CLEAN_REQREQ_UP And BBP_GET_STATUS _2 are running..
Check in RZ20 is there any error message for the follow on document.
Thanks
prasad.s

How to check whether follow on document is created for sc or po,is there any table or fm available?

How to check whether follow on document is created for sc or po,is there any table or fm available?

Hello Venu
Check FM: BBP_PD_SC_GETDETAIL and BBP_PD_PO_GETDETAIL table E_HEADER_REL
Check this: SRM Shopping cart and PO tables link
Regards

Linking multiple tables in numbers, how can I sort one table and this follow through on subsequent tables in the document?

I am a teacher setting up a tracking system using Numbers for the first time. I have set up a summary sheet with puil information, some of which is "looked up" from other tables within the document. It is working brilliantly until we regrouped the pupils.
When i reorganise the students on the summary page I want the same order to follow on all subsequent tables.
However the pupil lists on all subsequent pages stay in the original order!
Hope this makes some kind of sense as I am about to throw macbook out of the window!
DAve

davidmilce wrote:
I want all of the tick boxes in each row to move with the pupil name when they are reorganised (ie the unique data in each row stays with the pupi no matter where they go when sorted.
Thanks again
Dave
Dave,
I might use Match, Offset and Column in my expressions. There are many approaches to this
Match will tell you which row your person's data is in, and OFFSET will then take you to the row indicated by Match and the column indicated by COLUMN().
Let's say you want to access the data for Pupil A. Further assume that the string "Pupil A" is the content of Column A, essentially the title of the record.
MATCH(A, AF1 :: Table 1 :: A) will return the number of the Row in the source table where Pupil A is found.
INDEX(Main, MATCH($A, Main :: $A), COLUMN()) will get the content, in your case the checkbox status.
You are done if you are happy with displaying "TRUE" or "FALSE"
But if you want, you can substitute graphics, like this:
=IF(INDEX(Main, MATCH($A, Main :: $A), COLUMN()), "☑", "☐")
Regards,
Jerry

How to get MR Document from Billing Document at the table level

Hi All,
I am looking to find the MR Document based on which the Billing Document was generated. I need to find it out at the table level.
I looked into DBERCHZ2 table, but I can see a single billing document is linked to multiple Meter Reading Documents via different Line Items.
Could you guyz please help me? Am I seeing the right table? Is there any FM or ABAP program for the same?
Thanks a lot in advance.
Regards.

Hi ,
The link is Installation to get MR Doc from Bill Doc .
from ERCH-BELNR , fetch Contract (VERTRAg ) and then from EVER-VERTRAG get Installation (ANLAGE).
Get MR Doc(ABLBELNR) from EABLG based on EABLG-ANLAGE.
Thanks ,
Sachin

Follow-on documents: Display as Table to be set as default

Hello,
do you know please, how to set up:
Item data - Follow-on documents: a parameter Display as Table as default?
Normally is default: Display as Graphic, which is time consuming to be opened.
Thank you
Martin Dedouch

It is appropriate to move this thread from ERP-MM to [Enterprise Resource Planning (ERP)|Enterprise Resource Planning (SAP ERP);
Edited by: Jeyakanthan A on Jul 7, 2011 4:56 PM

In Requestor POWL, Shopping cart Related/Follow on documents should display as columns in POWL Table

Hello Experts,
Currently we are in SRM 7.02 implementation, for this we got requirement like below.
In Requestor POWL, Shopping cart related/follow on documents should display as columns in POWL. Please suggest me on this, how can i achieve this requirement. Thanks in advance.
1. we have Related/Follow on documents as shown in below screenshot.
2. As shown in above screenshot, these related/follow-on documents should show as columns in requestor POWL, as shown in below screenshot.
Thanks & Regards
Sivaram.

Hi Siva,
Take a look at the last part of the following document.
http://scn.sap.com/docs/DOC-25692
Regards,
Lisandro

AR DATA FLOW (TABLE LEVEL) - INVOICE편

제품 : FIN_AR
작성날짜 : 2003-09-16
AR DATA FLOW (TABLE LEVEL) - INVOICE편
=====================================
PURPOSE
이 문서에서는 AR table들에 대해 어떻게 data가 들어가는지에 대해
설명한다.
Invoice transaction을 기준으로 설명한다.
Explanation
1. Invoice
User가 invoice를 입력하면, 아래의 table들에 data가 insert된다.
o RA_CUSTOMER_TRX_ALL (Invoice Header)
o RA_CUSTOMER_TRX_LINES_ALL (Line Details)
o RA_CUST_TRX_LINE_GL_DIST_ALL (Information for posting to GL)
o RA_CUST_TRX_LINES_SALESREPS_ALL (Sales Credit Information)
일단, invoice가 "Complete"되면, 아래의 table에 한줄(혹은 그 이상)이
추가로 Insert된다.
o AR_PAYMENT_SCHEDULES_ALL (Running Totals for Invoice Amounts)
대체로 하나의 invoice는 하나의 Payment schedule record를 가지지만,
만약 할부(Installment)로 Pay처리되는 invoice라면, installment하나당
하나의 Payment schedule record를 가진다.
| | /| |
| TRX |---------------<-| PAYMENT |
| | \| SCHEDULE |
| |
| |
^ -------
/|\ |
------------ |
| | |
| TRX_LINES | |
_| | |
/ ------------ |
| | | |
\__/ | |
^ |
/|\ |
| |
| GL_DIST |
| |
1.1 RA_CUSTOMER_TRX_ALL
Invoice의 Header정보(Customer, Invoice Number, date.. etc)를 담고 있는 table이다.
Invoice하나당 한줄의 정보가 Insert된다.
Key = CUSTOMER_TRX_ID (generated from sequence RA_CUSTOMER_TRX_S)
Important Fields
TRX_NUMBER - User Entered Invoice Number
CUST_TRX_TYPE_ID - Foreign key to RA_CUST_TRX_TYPES
BILL_TO_CUSTOMER_ID - Foreign Key to RA_CUSTOMERS
SHIP_TO_CUSTOMER_ID - Foreign key to RA_CUSTOMERS
TRX_DATE - Invoice Date
COMPLETE_FLAG - Y or N
1.2 RA_CUSTOMER_TRX_LINES_ALL
Invoice의 Line정보(수금 item및 금액, Tax등)가 insert되는 table이다.
Invoice하나당 한줄이상을 가진다.
Key = RA_CUSTOMER_TRX_LINE_ID (from sequence RA_CUSTOMER_TRX_LINES_S)
Important Fields
CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
LINE_TYPE - LINE, TAX, FREIGHT
QUANTITY_INVOICED - Line Quantity
UNIT_SELLING_PRICE - Price per unit
EXTENDED_AMOUNT - Quantity * Price
LINK_TO_CUST_TRX_LINE_ID - Null for LINE, for TAX and FREIGHT lines
contains the RA_CUSTOMER_TRX_LINE_ID of
associated LINE record
1.3 RA_CUST_TRX_LINE_GL_DIST_ALL
GL로 Posting될 정보가 담겨져 있다.
Invoice Line당 한줄 + Invoice Header 한줄로 이루어져 있다.
(예를들어, Invoice의 Line이 총 3줄이라면, RA_CUST_TRX_LINE_GL_DIST_ALL table에는 총 4줄의 정보가 담기게 된다.)
Key = CUST_TRX_LINE_GL_DIST_ID (from sequence)
Important Fields
CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
CUSTOMER_TRX_LINE_ID - Foreign key to RA_CUSTOMER_TRX_LINES or
Null if this relates to Invoice Header.
AMOUNT - Value of distribution - entered currency
ACCOUNTED_AMOUNT - Value of distribution - book currency
CODE_COMBINATION_ID - Foreign key to GL_CODE_COMBINATIONS
POSTING_CONTROL_ID - -3 if unposted
GL_DATE - Accounting date.
GL_POSTED_DATE - Date Invoice posted to GL.
1.4 RA_CUST_TRX_LINE_SALESREPS_ALL
해당 invoice가 입력될때 함께 입력된 Sales Person에 대한 정보가
담겨져 있다.
1.5 AR_PAYMENT_SCHEDULES_ALL
해당 invoice에 대해서 Line, Tax, 운송비 등 각각의 항목에 대한 Total값과
Remaining값을 담고 있다.
대체로 Invoice당 한줄이 insert된다.
Key = PAYMENT_SCHEDULE_ID (from sequence AR_PAYMENT_SCHEDULES_S)
Important Fields
CUSTOMER_TRX_ID - Foreign key to RA_CUSTOMER_TRX
STATUS - (OP)en or (CL)losed
ACTUAL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise
date payment schedule closed.
GL_DATE_CLOSED - 31-DEC-4712 if still open, otherwise the
gl date of the closing transaction.
AMOUNT_DUE_ORIGINAL - Invoice Total Amount
AMOUNT_DUE_REMAINING - Total Amount outstanding for Invoice.
AMOUNT_LINE_ITEMS_ORIGINAL - Sum of Invoice Line amounts.
AMOUNT_LINE_ITEMS_REMAINING - Outstanding Line amounts.
TAX_ORIGINAL - Total Tax for Invoice.
TAX_REMAINING - Outstanding Tax for Invoice
FREIGHT_ORIGINAL - Total Freight For Invoice
FREIGHT_REMAINING - Outstanding Freight
AMOUNT_APPLIED - Total payments applied to this Invoice.
AMOUNT_CREDITED - Total Credit Memos applied.
AMOUNT_ADJUSTED - Total value of adjustments.
The payment schedule should balance within itself, ie the following
calculations
should be true:-
AMOUNT_DUE_ORIGINAL = AMOUNT_LINE_ITEMS_ORIGINAL
+ TAX_ORIGINAL
+ FREIGHT_ORIGINAL
AMOUNT_DUE_REMAINING = AMOUNT_LINE_ITEMS_REMAINING
+ TAX_REMAINING
+ FREIGHT_REMAINING
AMOUNT_DUE_ORIGINAL = AMOUNT_DUE_REMAINING
+ AMOUNT_APPLIED
- AMOUNT_CREDITED
+ AMOUNT_ADJUSTED
Reference Documents
Note : 29277.1

Hello,
The basic flow of data is
ERP tables - source snapshots - source views (eg MRP_AP%) - staging tables (MSC_ST%) - ODS tables ( MSC%)
Check out note 412375.1. This is the flow for sales order data for ASCP.
regards
Geert

Xchange Rate type changed in the follow on document getting posted from MM

Hi,
There is an issue while the follow on document posts from MM module to FI module.
The rate of exchange captured is M-CL while creation of the Purchase order. On posting the MIGO/ MIRO, the exchange rate type is correct viz M_CL .
But when the follow on document in the FI module is generated, the Exchange rate type is changed to M.
Can any one please tell me as to what can be the possible issue and wht are the configuration details be checked in the system or whether there is any special configuration of the Exchange rate type maintenence at country level and at transaction code level.
Thanks in Advance.
Manish

Hi Amam,
Have checked in the system the tocdes and the table as mentioned by you.
The issue here is that the system is picking the default M as the exchange rate type defined is blank . I want to specify the exchange rate type for a particular (country chile) for a particular document type.
Is there any setting to set the exchange rate ype at country / company code level for a particular document type .
Thanks in advance
Manish

Follow-up on u0093Fact Table VS. Dimension relative sizeu0094

You dont have to read the background info. below, it is only for reference. I have already gone though several links as such your touch in your own words will be much appreciated.
Can you help me understand these which came from the many links the Experts referred me .
1. For better performance: Use line item dimension where applicable, but use the "high cardinality" option with extreme care. Any clarification on high cardinality? And why with extreme care?
2. For better performance: 1. Make the Index perfect and create secondary index based on requirement.. I dont seem to follow this index issue being raised here.
Thanks.
--Background: References from these past postings ---
There is much to be said about performance in general, but I will try to answer your specific question regarding fact and dimension tables.
First of all try to compress as many requests as possible in the fact table and do that regularily.
Partition your compressed fact table physically based on for example 0CALMONTH. In the infocube maintenance, in the Extras menu, choose partitioning.
Partition your cube logically into several smaller cubes based on for example 0CALYEAR. Combine the cubes with a multiprovider.
Use constants on infocube level (Extras->Structure Specific Infoobject properties) and/or restrictions on specific cubes in your multiprovider queries if needed.
Create aggregates of subsets of your characteristics based on your query design. Use the debug option in RSRT to investigate which objects you need to include.
To investigate the size of the dimension tables, first use the test in transaction RSRV (Database Information about InfoProvider Tables). It will tell you the relative sizes of your dimensions in comparison to your fact table. Then go to transaction DB02 and conduct a detailed analysis on the large dimension tables. You can choose "table columns" in the detailed analysis screen to see the number of distinct values in each column (characteristic). You also need to understand the "business logic" behind these objects. The ones that have low cardinality, that is relate to each other shoule be located together. With this information at hand you can understand which objects contribute the most to the size of the dimension and separate the dimension.
Use line item dimension where applicable, but use the "high cardinality" option with extreme care.
Generate database statistics regularily using process chains or (if you use Oracle) schedule BRCONNECT runs using transaction DB13.
Good luck!
Kind Regards
Andreas
There are some simple things by which we can maintain the performance.
1> Make the Index perfect and create secondary index based on requirement.
2> Make statistics perfect.
3> Based on data size in dimenssion table use lineitem dimenssion.
HOpe this will help you.
Suneel

Hi Caud..
1] High Cardinality..
High Cardinality means that this dimension contains a large number of characteristic values. This information is used in accordance with the individual database platform in order to optimize performance. For example, an index type other than the standard may be used. Generally a dimension is perceived to have high cardinality when the dimension is at least 20% the size of the fact tables in terms of the number of entries each contain. Avoid marking a dimension as having high cardinality if you are in any doubt.
Cardinality creates indexes on the Dimension table entries and there by you would see an improvement in performance.
With Oracle DB, setting the Cardinality option causes a b-tree index to be built instead of a bitmap index even if it is not a line item dim.
Setting it as a Line Item dim also causes a b-tree index to be built instead of a bitmap index, but also embeds SID directly in the fact table, eliminating the dimension table.
As it changes from bit map to B-tree, u have to be careful as the SAP recommends the Bit map.
2]As indices increased the performance tremendously, u have to consider when ever the performance is main factor. it is very easy for query to access the data in the data target if it already indexed.
Refer this link..
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Hope it helps-
Regards-
MM
Assign points if it is useful, it is right way to say thanks.
Message was edited by: vishnuC

Getting a dumb after writing a SELECT statement at TABLE level of SMART

hi all,
i have created a RATE COMPARISON REPORT.In that Report i have to display Rate Price against RFQ No.For this purpose i have write a code at SMART FORMS in TABLE.Following are the code:
SELECT SINGLE netpr
INTO it_detail
FROM ekpo
INNER JOIN ekko ON
ekko~ebeln = ekpo~ebeln
WHERE ekko~BSTYP EQ 'F'
AND   ekko~spras eq 'E'
AND   ekpo~ebeln eq IT_DETAIL-EBELN
This code is assign with TEXT FILED at TABLE level.when i execute it i get the following dump.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CXSY_OPEN_SQL_DB', was not caught in procedure "%CO2" "(FORM)"_,
nor was it propagated by a RAISING clause.Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
The reason for the exception is:
In a SELECT access, the read file could not be placed in the target field provided. Either the conversion is not supported for   the type of the target field, the target field is too small to include the value, or the data does not have the format required for the target field.
could any body tell me what is problem in my SELECT query statement after executing giving me a dump.
Thanks,
sappk25

Hi
The select query is wrong, as you should not move the single field into a table (it_detail)....
Change the query as follows...
data: v_netwr type netwr.
SELECT SINGLE netpr
INTO v_netwr
FROM ekpo
INNER JOIN ekko ON
ekkoebeln = ekpoebeln
WHERE ekko~BSTYP EQ 'F'
AND   ekko~spras eq 'E'
AND   ekpo~ebeln eq IT_DETAIL-EBEL
if sy-subrc eq 0.
move v_netwr to it_detail.
endif.
Hope this helps....

Updation of contract data for all the follow up documents

In crm I have created a service contract. From this I have created a sales-service order as follow up document. Then from this service order one suspension order.
When I am opening the sales-service order in item details tab and then in contract tab we get the contract details. When i press the follow up document button and choose the suspension order the suspension order is opening and this contract details should come here also but it is not coming. Please suggest whether this can be done by configuration or by badi. If by badi then suggest its name.

Please not that the contract determination works fine when creating a new complaint ... but when the I am trying to create a complaint from service ticket the item level contract determination is not working fine ...
We have configured that the contract should be determined at the item level only option `F`.
I checked in one of the sap document that this cant be achieved by standard .
http://help.sap.com/saphelp_crm70/helpdata/en/46/5cd7335bbd516fe10000000a114a6b/frameset.htmhttp://help.sap.com/saphelp_crm70/helpdata/en/46/5cd7335bbd516fe10000000a114a6b/frameset.htm
Is there a way we can put this code in the BADI eg; CRM_SERVICE_CONTRACT ?? Please note that there is already an implementation of CRM_SERVICE_CONTRACT which is working fine for new service document creation .

Schema level and table level supplemental logging

Hello,
I'm setting up bi- directional DML replication between two oracle databases. I have enabled supplemental logging database level by running this command-
SQL>alter database add supplemental log data (primary key) columns;
Database altered.
SQL> select SUPPLEMENTAL_LOG_DATA_MIN, SUPPLEMENTAL_LOG_DATA_PK, SUPPLEMENTAL_LOG_DATA_UI from v$database;
SUPPLEME SUP SUP
IMPLICIT YES NO
-My question is should I enable supplemental logging table level also(for DML replication only)? should I run the below command also?
GGSCI (db1) 1> DBLOGIN USERID ggs_admin, PASSWORD ggs_admin
Successfully logged into database.
GGSCI (db1) 2> ADD TRANDATA schema.<table-name>
what is the deference between schema level and table level supplemental logging?

For Oracle, ADD TRANDATA by default enables table-level supplemental logging. The supplemental log group includes one of the following sets of columns, in the listed order of priority, depending on what is defined on the table:
1. Primary key
2. First unique key alphanumerically with no virtual columns, no UDTs, no functionbased
columns, and no nullable columns
3. First unique key alphanumerically with no virtual columns, no UDTs, or no functionbased
columns, but can include nullable columns
4. If none of the preceding key types exist (even though there might be other types of keys
defined on the table) Oracle GoldenGate constructs a pseudo key of all columns that
the database allows to be used in a unique key, excluding virtual columns, UDTs,
function-based columns, and any columns that are explicitly excluded from the Oracle
GoldenGate configuration.
The command issues an ALTER TABLE command with an ADD SUPPLEMENTAL LOG DATA clause that
is appropriate for the type of unique constraint (or lack of one) that is defined for the table.
When to use ADD TRANDATA for an Oracle source database
Use ADD TRANDATA only if you are not using the Oracle GoldenGate DDL replication feature.
If you are using the Oracle GoldenGate DDL replication feature, use the ADD SCHEMATRANDATA command to log the required supplemental data. It is possible to use ADD
TRANDATA when DDL support is enabled, but only if you can guarantee one of the following:
● You can stop DML activity on any and all tables before users or applications perform DDL on them.
● You cannot stop DML activity before the DDL occurs, but you can guarantee that:
❍ There is no possibility that users or applications will issue DDL that adds new tables whose names satisfy an explicit or wildcarded specification in a TABLE or MAP
statement.
❍ There is no possibility that users or applications will issue DDL that changes the key definitions of any tables that are already in the Oracle GoldenGate configuration.
ADD SCHEMATRANDATA ensures replication continuity should DML ever occur on an object for which DDL has just been performed.
You can use ADD TRANDATA even when using ADD SCHEMATRANDATA if you need to use the COLS option to log any non-key columns, such as those needed for FILTER statements and KEYCOLS clauses in the TABLE and MAP parameters.
Additional requirements when using ADD TRANDATA
Besides table-level logging, minimal supplemental logging must be enabled at the database level in order for Oracle GoldenGate to process updates to primary keys and
chained rows. This must be done through the database interface, not through Oracle GoldenGate. You can enable minimal supplemental logging by issuing the following DDL
statement:
SQL> alter database add supplemental log data;
To verify that supplemental logging is enabled at the database level, issue the following statement:
SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
The output of the query must be YES or IMPLICIT. LOG_DATA_MIN must be explicitly set, because it is not enabled automatically when other LOG_DATA options are set.
If you required more details refer Oracle® GoldenGate Windows and UNIX Reference Guide 11g Release 2 (11.2.1.0.0)

Maintaining Documents in plant level

Daer Folks,
Is there any possibility maintaining document at plant level without using LAB/OFFICE ? we have WERK(Plant) field in DRAW table but we are not assigning plant anywhere while creating document. is there any work around so that we can make use of plant field of DRAW to tale to restrict our document at plant level.
Bhuwan Tiwari

Hi,
regarding the field 'Plant' I have to inform you that this could not be filled duing the document creation process via transaction CV01N or the BAPI. So I would recommend you to use the field 'authorization group' for your requirement. This field can be filled with a specific value for each plant.
As soon as this field is filled you can define an authorization concept which only allows user to enter documents which have only a specific value in this field and so restrict all other user from entering. For further information on all existing authorization objects for DMS and also regarding the field Authorization Group please see the following link too:
http://wiki.sdn.sap.com/wiki/display/PLM/AuthorizationObjectsin+DMS
Best regards,
Christoph

Details of Follow-up documents at Table level

Similar Messages

Maybe you are looking for