ChaRM-Table for 'Due By' Date in RFC

[Former Member]

Hi ,

In RFC(Request for change) screen  we have 'Due By' Date. In which table it is saved.

Regrds

P Kumar

[Former Member · Accepted solution]

Hi Mr. Kumar.

I do not know why they made it so complicated, but there is a logical reason behind that, which I would like to learn one day from the extreme, structured, and organize German brains.

Dates in general in CRM are stored in table SCAPPTSEG, but there is a path to follow to get from one end to the other. 

(remember that behind the scenes SolMan is a CRM system)

Let's discover that path together with an example.

We created an RfC, which we basically open to only populate Due by, after which we pressed Save just to get the RfC number added and your Due by entry stored. FYI, we are assigning the RfC number after we save the first time.

 

Let's look for the content of table CRMD_ORDERADM_H, in particular for OBJECT_ID 7000000173. As you can see the internal GUID given to our document or business transaction is:  001E0BEA00C41EE38AED7582CF2AE8E1

Now let's see the correspondent entries in CRMD_LINK

Grouping the entries together the way they better relate we have:

As you can see there are five *SET GUID objects created for our RfC GUID 001E0BEA00C41EE38AED7582CF2AE8E1.

Why 05 on the HI and the other numbers on the SET sides, respectively?

That comes from table CRMC_OBJECTS:

We could pause for a while to get to know more this table, but let's stay focused being the only entry we care about here Dates, as that is your question.  Therefore, 05,  because our RfC is a ORDERADM_H document or business transaction (remember we started our path with table CRMD_ORDERADM_H?), and 30, because we want to know where Datesare stored.     So, based on that focus, the only GUID we should consider at this moment is 001E0BEA00C41EE38AED7582CF2B48E1, which is the one in the line with 30.

Let's visit table SCAPPTSEG to see how many entries were created for that GUID.

How do we know the SRV_RREADY corresponds to Due by?  That comes from Date Management in CRM. SPRO: CRM > Basic Functions > Date Management > Define Date Profile.

And let me guess your next question? Well, how do I know that SRV_RREADY corresponds to Due by? That the field Due by is related to SRV_RREADY?  For this exercise we know they related because the date we used "Dec 8, 2013", no ones has used in our installation, so we know for sure that the record we found is the correct one,  and also because of the chain of links that took us there.

Personally, I do not know the exact answer, yet, but let me take you a little closer hoping somebody can give us the final connection of these dots to complete the path.

You know that by pressing <F2> in the web ui you can get some extra details

With that information, we launch transaction BSP_WD_CMPWB and display the component AIC_CMCR_H, open up the view, and get to the context node we found.

Well, within that Implementation class or in the Attribute, there is a piece of code or attributes that will hook the pieces together, either being a definition on the field BRDATEDUEBY or something that when the record is to be saved in the table SCAPPTSEG, uses that SRV_RREADY as APPT_TYPE.  Probably somebody with time could give us a hand or you Mr. Kummar if you happen to be a BSP developer, or one of your colleagues.  If not, I will try to do it when time permits.

My pleasure,

Juan-Carlos Garcia-Garavito

[Former Member · Accepted solution]

Hi Juan,

You can get the due by date from table SCAPPTSEG.

Cross refer GUID from table CRMD_ORDERADM_H.

Regards

PK

[Former Member · Accepted solution]

Hi there:

Just in case, we add a link below of a blogpost that is in the process of being approved, in which we added more tables and a more logical view of the whole solution.

http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/10/08/sap-charm-basic-busi...

Two main component sets are part of the diagram: 

1. Business Partner, where you find the tables with data related to the BP, identification, HR related information, etc.
2. Transaction, where you find the tables that store most of the Business Transaction related data, including our own customer developments.

It is important to mention that within each box, we placed the main table fields that server as connectors between tables, following the arrows.    Kind of foreign keys.

It is very important to mention that there is an extra resource you may already know.  The report CRM_ORDER_READ.  In that report, you provide a Business Transaction and you will obtain the list of tables that contain records that pertain to that BT in particular.    Unfortunately, the report does not give you a connection between an RfC (ZMCR) and its own Change Objects (ZMMJs), or between either of them and their date field values.  At that moment is when the provided diagram gives you the complementary assistance to hook up the pieces together.

We hope the diagram becomes beneficial for you and any feedback to make it better is very appreciated.

Our apologies for the colors.  There was no inspiration for that today.   Only pairs of tables that fulfill the same task were gathered together under the same color.

Regards,    

Juan-Carlos Garcia-Garavito