SAP EH &S SVT Tables and fields for SVT REACH EXP scenario ??

[satya11719]

Hi,

I need help on SVT EXP delivery scenario i was configured for delivery scenario and i have some doubts on related filed and tables.

I need to track delivered quantities to Europe (Finished product is not registered only Raw materials using registered need to track RM)

which field i can us for delivery scenario

Table       field

LIKP          ?

LIPS          ?

VBPA         ?

VBUP        ?

MKPF        ?

MSEG        ?

If 50 deliveries are created per how can i that this delivery is related to my tracking substance if answer from SVT flat from MM, they we can determine that in SALES ORDER level,

I maintain Z Specification composition in legal composition and A,B,C,D present in that and i maintain registered quantity legal entity and regulation in component level and i just assigned the material to Z specification.

My question to track shall i maintain compostion components as list_sub or pure_sub.

Next thing when i entered  CBRC20 given regulation as REACH and executed(witch out giving scenario) it is automatically showing the IMP scenario for Purchase and Purchase quantity is automatically updated ....now i need to change monitored values to EXP and delivery scenario which configuration i need to do for that or shall i maintain any environmental parameters for that.

please help why i'm getting IMP scenario in CBRC20 as default and how can i change that to EXP.

Thanks

Satya

[christoph_bergemann]

Dear Satya

did you check my hints in thread

You are now "lost" in SVT area to a certain extent)

Therefore I will provide some help; but please the other thread as well:

a.) My question to track shall i maintain compostion components as list_sub or pure_sub.

=> you can do set uphow you would like to do it. In most cases if you use standard SAP data model REAL_SUB contains PURSE_SUB contains LIST_SUB; so in most cases LIST_SUB will be tracked

b.)

Next thing when i entered CBRC20 given regulation as REACH and executed(witch out giving scenario) it is automatically showing the IMP scenario for Purchase and Purchase quantity is automatically updated ....now i need to change monitored values to EXP and delivery scenario which configuration i need to do for that or shall i maintain any environmental parameters for that.

please help why i'm getting IMP scenario in CBRC20 as default and how can i change that to EXP.

=> you should ask your self: why do you get results" for IMP (do you get for PROD as well?) After some "thinking" you might realizes that

1.) a job is missing (could be)

2.) master data is missing (could be)

3.) or customizing set up is wrong (could be)

So that you can not see "EXP" data

d.)

If 50 deliveries are created per how can i that this delivery is related to my tracking substance if answer from SVT flat from MM, they we can determine that in SALES ORDER level,

=> this part I did not asnwer yet: story is system check if logistic document is "SVT relevant". if yes then it uses the materials in the document a try to find real_SUB etc. Then system check CCRCT_EHS_COMP" and retrieves composition and starts calculating. E.g. you hav 1 t and two components. Therefore per component the system will add 500kg to the components whatever values has been "tracked" in the past

I maintain Z Specification composition in legal composition and A,B,C,D present in that and i maintain registered quantity legal entity and regulation in component level and i just assigned the material to Z specification.

I do not understand your definition of "Z composition". but the story is as:

You have a REAL_SUB

You have used composition "Legal Composition" to set up "SVT" relevant composition

Onlevel of components A; B, ... you have entered registered volume per company code

=> but what about material assignment? In general: This set up is correct

C.B.

PS: the tables you have mentioned and the picture you have used is the "critical" part to do the set up of EXP scenario; as explained in the different thread: as long as you do not understand "SAP SD" process and why we have two scenarios (which you can use potentially) in SVT and why the tables as listed are listed there.. You should not go on and ask a SAP SD guy for help; he will explain "easily"; the "but" is: you must discuss with your customer "how should be tracked" (which sales delivery...) and then the set up as such is done (if you use STANDARD) quite quick (TOPIC OF JOB: REFER ABOVE; DON'T FORGET !)

[satya11719]

Really Kudos CB,***

Thank you very much for your patience & time for crystal clear explanation.

Let me check on by one.

And congratulation for your achievement,

You will be always leader for US*

Thanks

Satya              

[christoph_bergemann]

Dear Satya

you are on good track in EHS. SVT is not the "easy" sub module to learn.

Honestly: based on your "historic" activities using SAP applications: EHS SVT can be a real challenge  (if you have no or less experience in SAP MM, SAP SD, SAP PP etc.) for somebody acting "only" in EHS.

From integration point of view. here SVT is the "most complex" one. EHS DG is "only" integrated in SAP SD, same for SAP SAF (report distrbution); only GLM has similar links to SAP SD, SAP PP

There are enough challenges now and in future to learn (e.g. S/4 HANA)  and step by step then you can share your "leasons learned" etc. here (as you have still done in

BOMBOS is as well a kind of "special" area.

I have corrected one of my answers above That was an error on my side. Parameter SVT_CLASS_PRAEFIX was defined correct by you.

C.B.

PS: any progress in your parallel threads as: e.g.

[christoph_bergemann]

Dear Satya

any update here? Can we assume that topic is solved?

C.B.

[satya11719]

No progress till now, i was executed program RREGCH_EVALUATION ,

Check this evaluation

20.05.2016                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         INTERNAL: Substance Volume Tracking: Evaluation of Settings                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                1

General Data

Table: TCGENV

Description: EHS: General Environment Parameters

  MANDT PARAM ORD VALUE INTERN

  444 SVT_ARCHIVE_PLAN_DATA 0000 REACH;X

  444 SVT_ARCHIVE_PLAN_DATA 0001 REACH_EU;X

  444 SVT_CLASS_PREFIX 0000 SAP

  444 SVT_EHS_RFCDEST 0000

  444 SVT_FUNC_TRACE_MSG 0000

  444 SVT_MATERIAL_CLASS 0000 ZRCS_REACH_REL

  444 SVT_NOTICHCK_PHR_BANNED 0000

  444 SVT_NOTICHCK_PHR_NEG 0000

  444 SVT_NOTICHCK_PHR_NOT_BANNED 0000

  444 SVT_NOTICHCK_PHR_PO 0000

  444 SVT_PHR_NEG 0000 CUST-Z15.00800580

  444 SVT_PHR_POL_INDICAT 0000

  444 SVT_PHR_POS 0000 CUST-Z15.00800590

  444 SVT_PHR_SPEEXCL_REG 0000

  444 SVT_SO_PROFILE 0000 EHS_SO

  444 SVT_SO_STATUS 0000 E0001

  444 SVT_SUBID_F4_FUNC 0000

  444 SVT_TRACKING_DIFF_TIME 0000

  444 SVT_WL_OFFLINE 0000 X

Table: TCG81

Description: EHS: Regulatory List

  MANDT SLSTID SLSTDIS SLSTDAT SLSTVER SLSTRES RVLID REM SLSTLAN SLSTSID SLSTSCH NEGATIVFLG

  444 REACH_EU 00.00.0000

Table: CCRCC_DET

Description: EHS: Data Determination Modules per Regulation/Scenario

  MANDT REG SCEN BASE_UNIT FLG_PERIOD FCT_TRACK FCT_MATNR_GET FCT_SUBID_GET FCT_CMP_TREE USEXNAM USEXPAR CMP_ESTCAT VACLID RVLID FCT_CONDENSE FCT_PLAN_SAVE FCT_CONF_SAVE FCT_PROCESS_EXE FLG_HIST TRACK_PACK CMP_ESTCAT2 VACLID2 RVLID2 VATSPECEXCL CHARSPECEXCL REGSPECEXCL POLYMONO_TRANS

  444 REACH_EU EXP TO X CBRC_SO_DATA_TRACK CBRC_MM_REL_MATNR_FILTER CBRC_LIB_SPEC_FROM_MAT_GET CBRC_LIB_TRACK_SUBST_GET SAP_EHS_1012_024 REACH REG_REACH CBRC_SO_DATA_CONDENSE CBRC_SO_PLANNED_DATA_SAVE CBRC_SO_CONFIRMED_DATA_SAVE X 0000 SAP_EHS_1012_003 REACH REG_REACH

Table: CCRCC_DETDOCTYPE

Description: EHS: Modules for Regulation/Scenario/Scenario Category

  MANDT REG SCEN DOCTYPE FCT_PLAN_GET FCT_CONF_GET FCT_DATA_FILL FCT_DATA_SEP FCT_KEY_BUILD FCT_KEY_SPLIT

  444 REACH_EU EXP DELIVERY CBRC_SO_PL_DATA_READ CBRC_SO_CO_DATA_READ CBRC_SO_DATA_FILL CBRC_SO_DATA_SEP_BY_VA CBRC_LIB_KEY_BUILD CBRC_LIB_KEY_SPLIT

Table: CCRCC_FILTER

Description: EHS: Data Filtering

  MANDT REG SCEN TABNAME FIELD ORD SIGN SELOPTION LOW HIGH

  444 REACH_EU EXP LIKP LFART 0000 I EQ ZEXD

  444 REACH_EU EXP LIKP VBTYP 0000 I EQ J

  444 REACH_EU EXP LIKP VKORG 0000 I EQ 2000

  444 REACH_EU EXP LIPS LFIMG 0000 I EQ

  444 REACH_EU EXP LIPS MEINS 0000 I EQ

  444 REACH_EU EXP MKPF VGART 0001 I EQ SH

  444 REACH_EU EXP VBAK AUART 0000 I EQ ZEXO

  444 REACH_EU EXP VBAK AUART 0001 I EQ

  444 REACH_EU EXP VBAK AUART 0003 I EQ SO

  444 REACH_EU EXP VBAK AUART 0004 I EQ C

  444 REACH_EU EXP VBAK VBELN 0001 I EQ SO

  444 REACH_EU EXP VBAK VKORG 0000 I EQ 2000

  444 REACH_EU EXP VBPA KUNNR 0003 I EQ SP

  444 REACH_EU EXP VBPA PARVW 0000 I EQ SH

  444 REACH_EU EXP VBPA PARVW 0002 I EQ BP

Table: CCRCC_LIMITG

Description: EHS: General Quantity Restriction

  MANDT REG REGLEVEL SCEN LOW UPP UOM PERIOD

  444 REACH_EU 1     0.0000     1.0000 TO

  444 REACH_EU 2     1.0000   100.0000 TO

  444 REACH_EU 3    10.0000   100.0000 TO

  444 REACH_EU 4   100.0000 999999.9990 TO

  444 REACH_EU 5 1,000.0000 999999.9999 TO

Table: CCRCC_LIMITS

Description: EHS: Relative Quantity Restriction

  MANDT REG REGLEVEL SCEN MSGTYPE REL_LIMIT FLG_DISP FLG_MAIL FLG_BLOCK

  444 REACH_EU 1 1 070 X

  444 REACH_EU 1 2 090 X X

  444 REACH_EU 1 3 100 X X X

  444 REACH_EU 2 1 070 X

  444 REACH_EU 2 2 090 X X

  444 REACH_EU 2 3 100 X X X

  444 REACH_EU 3 1 070 X

  444 REACH_EU 3 2 090 X X

  444 REACH_EU 3 3 100 X X X

  444 REACH_EU 4 1 070 X

  444 REACH_EU 4 2 090 X X

  444 REACH_EU 4 3 100 X X X

  444 REACH_EU 5 1 070 X

  444 REACH_EU 5 2 090 X X

  444 REACH_EU 5 3 100 X X X

Table: CCRCC_CHCK_ON

Description: EHS: Online Checks for Regulation/Scenario/Scenario Category

  MANDT REG SCEN DOCTYPE FCT_CHK_RELEVANT FCT_CHK_AMOUNT FCT_CHK_LIMITS FCT_CHK_BLOCK FCT_CHK_MSG_COLL FCT_CHK_MSG_DISP FCT_CHK_MSG_MAIL

  444 REACH_EU EXP DELIVERY CBRC_PURREQ_CHCK_RELEVANT CBRC_CHK_AMOUNTS_GEN_DET CBRC_CHK_AMOUNTS_GEN_LIMITS CBRC_PURREQ_DOCUMENT_BLOCK CBRC_CHK_ONLINE_GEN_MESSAGES CBRC_PURREQ_MSG_DISPLAY CBRC_CHK_MESSAGES_MAIL

  444 REACH_EU EXP SALES CBRC_PUR_CHCK_RELEVANT CBRC_CHK_AMOUNTS_GEN_DET CBRC_CHK_AMOUNTS_GEN_LIMITS CBRC_PUR_DOCUMENT_BLOCK CBRC_CHK_ONLINE_GEN_MESSAGES CBRC_PUR_MSG_DISPLAY CBRC_CHK_MESSAGES_MAIL

Table: TJ30T

Description: Texts for User Status

  MANDT STSMA ESTAT SPRAS TXT04 TXT30 LTEXT

  444 EHS_PRO E0001 DE PROD Produktionsauftrag

  444 EHS_PRO E0001 EN PROD Manufacturing Order

  444 EHS_SO E0001 DE SD Verkaufsauftrag

  444 EHS_SO E0001 EN SD Sales Order

Table: CCRCC_EXCHG

Description: EHS: Data Transfer from and to EH&S

  MANDT REG FCT_FILL_FR_EHS FCT_MAP_FR_EHS FCT_SAVE_FR_EHS FCT_FILL_TO_EHS FCT_SAVE_TO_EHS FCT_FILL_OR_DATA

  444 REACH_EU CBRC_EHS_FILL_EHS_DATA CBRC_EHS_FILL_MAP CBRC_LIB_SVT_TABLE_SAVE CBRC_EHS_MAP_FILL_ARCHIVE CBRC_EHS_TRACKED_DATA_SAVE

Table: CCRCC_MON

Description: EHS: Monitoring Settings

  MANDT REG SCEN DOCTYPE FCT_CHK_AMOUNT FCT_CHK_LIMITS FCT_MON_ICON FCT_MON_DISPL FCT_MON_ADD_INFO

  444 REACH_EU CBRC_CHK_AMOUNTS_GEN_DET CBRC_CHK_AMOUNTS_GEN_LIMITS CBRC_MON_ICON_SET CBRC_MON_DATA_DISPLAY CBRC_MON_INFO_IDENT_ADD

Table: CCRCT_RUN

Description: Time stamp of Tracking and Filling Runs

  MANDT ACTION REG SCEN START_DATE START_TIME END_DATE END_TIME

  444 FILLING REACH_EU 01.01.2015 00:00:00 11.05.2016 18:56:27

  444 TRACKING REACH_EU EXP 01.01.2016 00:00:00 12.05.2016 15:24:32

  444 TRACKING REACH_EU IMP 26.04.2016 00:00:00 29.04.2016 13:49:54

Table: CCRCC_PERIOD

Description: EHS: Period Definition

  MANDT PERIOD REG SDAY SMONTH EDAY EMONTH

  444 Q1 REACH_EU 01 01 31 03

  444 Q2 REACH_EU 01 04 30 06

  444 Q3 REACH_EU 01 07 30 09

  444 Q4 REACH_EU 01 10 31 12

Table: CCRCC_ERRMAIL

Description: EHS: Specify Recipients for Error Messages

  MANDT REG BUKRS DOCTYPE DOCCAT REG_LEVEL MSGTYPE RECTYPE RECNAME RFCDEST LANGU RECEIVER

  444 REACH_EU DELIVERY B EN EHSCONS

  444 REACH_EU SALES B EN techserv_to@rajgrp.com

Table: CCRCC_SCENTYPE

Description: EHS: Scenario-to-Scenario-Category Assignment

  MANDT SCEN DOCTYPE

  444 CON PRODUCTION

  444 EXP DELIVERY

  444 EXP SALES

  444 IMP PURCHASE

  444 IMP PURCHASE_REQUISITION

  444 PRO PRODUCTION

  444 PUR PURCHASE

  444 PUR PURCHASE_REQUISITION

  444 SO DELIVERY

  444 SO SALES

Table: CCRCC_CHCK_SALES

Description: EHS: Activate Check of Sales Orders

  MANDT ORD FCT_CHK_SALES FLG_CHK_SALES

  444 0001 CBRC_EXIT_47_SO X

Table: T006

Description: Units of Measurement

  MANDT MSEHI KZEX3 KZEX6 ANDEC KZKEH KZWOB KZ1EH KZ2EH DIMID ZAEHL NENNR EXP10 ADDKO EXPON DECAN ISOCODE PRIMARY TEMP_VALUE TEMP_UNIT FAMUNIT PRESS_VAL PRESS_UNIT

  444 KG X X   3 X MASS         1         1   0  0.000000   0   0 KGM X 0.0000000000000000E+00 0.0000000000000000E+00

  444 MT X X   3 X MASS     1,000         1   0  0.000000   0   0 TNE 0.0000000000000000E+00 0.0000000000000000E+00

  444 TO X X   3 X MASS     1,000         1   0  0.000000   0   0 TNE X 0.0000000000000000E+00 0.0000000000000000E+00

  444 KT X X   0 X MASS 1,000,000         1   0  0.000000   0   0 0.0000000000000000E+00 0.0000000000000000E+00

  444 TON X X   0 X MASS     4,536         5   0  0.000000   0   0 0.0000000000000000E+00 0.0000000000000000E+00

  444 G X X   3 X MASS         1     1,000   0  0.000000   0   0 GRM X 0.0000000000000000E+00 0.0000000000000000E+00

  444 OZ X X   0 X MASS       567    20,000   0  0.000000   0   0 0.0000000000000000E+00 0.0000000000000000E+00

  444 MG X X   3 X MASS         1 1,000,000   0  0.000000   0   0 MGM X 0.0000000000000000E+00 0.0000000000000000E+00

  444 LB X X   0 X MASS   453,592 1,000,000   0  0.000000   0   0 0.0000000000000000E+00 0.0000000000000000E+00

  444 mgm X X   0 X MASS         1         1   0  0.000000   0   2 MGM 0.0000000000000000E+00 0.0000000000000000E+00

  444 ONE X X   0 PROPOR         1         1   0  0.000000   0   0 0.0000000000000000E+00 0.0000000000000000E+00

  444 % X X   0 X PROPOR         1       100   0  0.000000   0   0 P1 0.0000000000000000E+00 0.0000000000000000E+00

  444 %O X X   0 X PROPOR         1     1,000   0  0.000000   0   0 0.0000000000000000E+00 0.0000000000000000E+00

  444 PPT X X   0 X PROPOR         1         1 -12  0.000000   0   0 0.0000000000000000E+00 0.0000000000000000E+00

  444 PPB X X   0 X PROPOR         1         1 -9  0.000000   0   0 0.0000000000000000E+00 0.0000000000000000E+00

  444 PPM X X   0 X PROPOR         1         1 -6  0.000000   0   0 59 0.0000000000000000E+00 0.0000000000000000E+00

[christoph_bergemann]

Dear Satya

quite lengthy information which comes from the report (but this is the reason why we have the report):

I will answer per "block" (or try to do so:

This is the "environment paramter" customizing block

444 SVT_ARCHIVE_PLAN_DATA 0000 REACH;X  => as long as there is no "tracking" resiult we can ignore this

  444 SVT_ARCHIVE_PLAN_DATA 0001 REACH_EU;X => as long as there is no "tracking" resiult we can ignore this

  444 SVT_CLASS_PREFIX 0000 SAP => this is corect

  444 SVT_EHS_RFCDEST 0000 => assuming you run EHS and SAP ERP in the same system;: you need not to take care here

  444 SVT_FUNC_TRACE_MSG 0000 => not relevent for the "problem

  444 SVT_MATERIAL_CLASS 0000 ZRCS_REACH_REL => this is correct

  444 SVT_NOTICHCK_PHR_BANNED 0000 => not relevant as long as you do not use "notification check"

  444 SVT_NOTICHCK_PHR_NEG 0000 => not relevant as long as you do not use "notification check"

  444 SVT_NOTICHCK_PHR_NOT_BANNED 0000 => not relevant as long as you do not use "notification check"

  444 SVT_NOTICHCK_PHR_PO 0000 => not relevant as long as you do not use "notification check"

  444 SVT_PHR_NEG 0000 CUST-Z15.00800580 => THIS IS IMPORTANT: IT IS ASSUMED: YOU HVAE THIS PHRASE IN THE SYSTEM

  444 SVT_PHR_POL_INDICAT 0000 => only of interest if you need to check polymers; you should improve here

  444 SVT_PHR_POS 0000 CUST-Z15.00800590 THIS IS IMPORTANT: IT IS ASSUMED: YOU HVAE THIS PHRASE IN THE SYSTEM

  444 SVT_PHR_SPEEXCL_REG 0000 => only of interest if you would liek to"exclude" a spec from tracking

  444 SVT_SO_PROFILE 0000 EHS_SO => not of interest in relation to your problem

  444 SVT_SO_STATUS 0000 E0001 => not of interest in relation to your problem

  444 SVT_SUBID_F4_FUNC 0000 => not of interest in relation to your problem

  444 SVT_TRACKING_DIFF_TIME 0000 => not of interest in relation to your problem

  444 SVT_WL_OFFLINE 0000 X => CHECK YOUR JOBS (three reports must be up and running; look omn OSS note)

C.B.

PS: at two places my answer was wrong, sorry. I corrected it.

[christoph_bergemann]

Dear Satya

444 REACH_EU EXP TO X CBRC_SO_DATA_TRACK CBRC_MM_REL_MATNR_FILTER CBRC_LIB_SPEC_FROM_MAT_GET CBRC_LIB_TRACK_SUBST_GET SAP_EHS_1012_024 REACH REG_REACH CBRC_SO_DATA_CONDENSE CBRC_SO_PLANNED_DATA_SAVE CBRC_SO_CONFIRMED_DATA_SAVE X 0000 SAP_EHS_1012_003 REACH REG_REACH

=> more or less standard function modules used. As staring point ok

C.B.

[christoph_bergemann]

Dear Satya

Table: CCRCC_DETDOCTYPE

Description: EHS: Modules for Regulation/Scenario/Scenario Category

  MANDT REG SCEN DOCTYPE FCT_PLAN_GET FCT_CONF_GET FCT_DATA_FILL FCT_DATA_SEP FCT_KEY_BUILD FCT_KEY_SPLIT

  444 REACH_EU EXP DELIVERY CBRC_SO_PL_DATA_READ CBRC_SO_CO_DATA_READ CBRC_SO_DATA_FILL CBRC_SO_DATA_SEP_BY_VA CBRC_LIB_KEY_BUILD CBRC_LIB_KEY_SPLIT

=> more or less standard function modules used. As starting point ok

C.B.

PS: if you would like to dig deeper the "Sales" part of "EXP" scenario you neeed additionaly entries with "SALES" => please improve here !

[christoph_bergemann]

Dear Satya

this now is the "heart" of SVT:logic (the "starting point in selecting the relevant logistic documents)

table: CCRCC_FILTER

Description: EHS: Data Filtering

  MANDT REG SCEN TABNAME FIELD ORD SIGN SELOPTION LOW HIGH

  444 REACH_EU EXP LIKP LFART 0000 I EQ ZEXD

  444 REACH_EU EXP LIKP VBTYP 0000 I EQ J

444 REACH_EU EXP LIKP VKORG 0000 I EQ 2000

  444 REACH_EU EXP LIPS LFIMG 0000 I EQ

444 REACH_EU EXP LIPS MEINS 0000 I EQ

  444 REACH_EU EXP MKPF VGART 0001 I EQ SH

  444 REACH_EU EXP VBAK AUART 0000 I EQ ZEXO

  444 REACH_EU EXP VBAK AUART 0001 I EQ

  444 REACH_EU EXP VBAK AUART 0003 I EQ SO

  444 REACH_EU EXP VBAK AUART 0004 I EQ C

  444 REACH_EU EXP VBAK VBELN 0001 I EQ SO

  444 REACH_EU EXP VBAK VKORG 0000 I EQ 2000

  444 REACH_EU EXP VBPA KUNNR 0003 I EQ SP

  444 REACH_EU EXP VBPA PARVW 0000 I EQ SH

  444 REACH_EU EXP VBPA PARVW 0002 I EQ BP

Looking on this: ypur sales order must fullfill:

444 REACH_EU EXP VBAK AUART 0000 I EQ ZEXO

  444 REACH_EU EXP VBAK AUART 0001 I EQ

  444 REACH_EU EXP VBAK AUART 0003 I EQ SO

  444 REACH_EU EXP VBAK AUART 0004 I EQ C

  444 REACH_EU EXP VBAK VBELN 0001 I EQ SO

  444 REACH_EU EXP VBAK VKORG 0000 I EQ 2000

and on top:

  444 REACH_EU EXP VBPA KUNNR 0003 I EQ SP

  444 REACH_EU EXP VBPA PARVW 0000 I EQ SH

  444 REACH_EU EXP VBPA PARVW 0002 I EQ BP

So your sakes ordeer must be located in sales organisaiton 2000 and sales order type can be "ZEXO" "C", "CO"; the "blank" value does not make sense

Does your sales order fulfill this?

C.B.

PS: values 444 REACH_EU EXP LIPS MEINS 0000 I EQ

is strange. LIPS is teh "delivery" part; and "meins" the "UOM" part (here we are on "position" level. But why you check for "space"?

Same here:  444 REACH_EU EXP LIPS LFIMG 0000 I EQ

YOu should "recheck"here your set up and contaxt a SAP SD expert knowing the set up of SAP SD module as used

[christoph_bergemann]

Dear Satya

able: CCRCC_LIMITG

Description: EHS: General Quantity Restriction

  MANDT REG REGLEVEL SCEN LOW UPP UOM PERIOD

  444 REACH_EU 1     0.0000     1.0000 TO

  444 REACH_EU 2     1.0000   100.0000 TO

  444 REACH_EU 3    10.0000   100.0000 TO

  444 REACH_EU 4   100.0000 999999.9990 TO

  444 REACH_EU 5 1,000.0000 999999.9999 TO

Not of interest in context of your issue

same :

Table: CCRCC_LIMITS

Description: EHS: Relative Quantity Restriction

  MANDT REG REGLEVEL SCEN MSGTYPE REL_LIMIT FLG_DISP FLG_MAIL FLG_BLOCK

  444 REACH_EU 1 1 070 X

  444 REACH_EU 1 2 090 X X

  444 REACH_EU 1 3 100 X X X

  444 REACH_EU 2 1 070 X

  444 REACH_EU 2 2 090 X X

  444 REACH_EU 2 3 100 X X X

  444 REACH_EU 3 1 070 X

  444 REACH_EU 3 2 090 X X

  444 REACH_EU 3 3 100 X X X

  444 REACH_EU 4 1 070 X

  444 REACH_EU 4 2 090 X X

  444 REACH_EU 4 3 100 X X X

  444 REACH_EU 5 1 070 X

  444 REACH_EU 5 2 090 X X

  444 REACH_EU 5 3 100 X X X

This you will need all later (f tracking is up and running etc.) and you get tracking resutls

C.B.

[christoph_bergemann]

Dear Satya

MANDT REG SCEN DOCTYPE FCT_CHK_RELEVANT FCT_CHK_AMOUNT FCT_CHK_LIMITS FCT_CHK_BLOCK FCT_CHK_MSG_COLL FCT_CHK_MSG_DISP FCT_CHK_MSG_MAIL

  444 REACH_EU EXP DELIVERY CBRC_PURREQ_CHCK_RELEVANT CBRC_CHK_AMOUNTS_GEN_DET CBRC_CHK_AMOUNTS_GEN_LIMITS CBRC_PURREQ_DOCUMENT_BLOCK CBRC_CHK_ONLINE_GEN_MESSAGES CBRC_PURREQ_MSG_DISPLAY CBRC_CHK_MESSAGES_MAIL

  444 REACH_EU EXP SALES CBRC_PUR_CHCK_RELEVANT CBRC_CHK_AMOUNTS_GEN_DET CBRC_CHK_AMOUNTS_GEN_LIMITS CBRC_PUR_DOCUMENT_BLOCK CBRC_CHK_ONLINE_GEN_MESSAGES CBRC_PUR_MSG_DISPLAY CBRC_CHK_MESSAGES_MAIL

This is wrong; you comine "EXP" entries with "import" entries does not make sense => you must correct here

C.B.

[christoph_bergemann]

Dear Satya

Table: TJ30T

Description: Texts for User Status

  MANDT STSMA ESTAT SPRAS TXT04 TXT30 LTEXT

  444 EHS_PRO E0001 DE PROD Produktionsauftrag

  444 EHS_PRO E0001 EN PROD Manufacturing Order

  444 EHS_SO E0001 DE SD Verkaufsauftrag

  444 EHS_SO E0001 EN SD Sales Order

this you need to take care later if EXP us up and running

C.B:

[christoph_bergemann]

Dear Satya

Table: CCRCC_EXCHG

Description: EHS: Data Transfer from and to EH&S

  MANDT REG FCT_FILL_FR_EHS FCT_MAP_FR_EHS FCT_SAVE_FR_EHS FCT_FILL_TO_EHS FCT_SAVE_TO_EHS FCT_FILL_OR_DATA

  444 REACH_EU CBRC_EHS_FILL_EHS_DATA CBRC_EHS_FILL_MAP CBRC_LIB_SVT_TABLE_SAVE CBRC_EHS_MAP_FILL_ARCHIVE CBRC_EHS_TRACKED_DATA_SAVE

this is teh "heart" of the "filling" report => anything is here standard

C.B.

[christoph_bergemann]

Dear Satya

Table: CCRCC_MON

Description: EHS: Monitoring Settings

  MANDT REG SCEN DOCTYPE FCT_CHK_AMOUNT FCT_CHK_LIMITS FCT_MON_ICON FCT_MON_DISPL FCT_MON_ADD_INFO

  444 REACH_EU CBRC_CHK_AMOUNTS_GEN_DET CBRC_CHK_AMOUNTS_GEN_LIMITS CBRC_MON_ICON_SET CBRC_MON_DATA_DISPLAY CBRC_MON_INFO_IDENT_ADD

here you use "scenario" independent set up... there might be the need to improve later

C.B.

[christoph_bergemann]

Dear Satya

Table: CCRCT_RUN

Description: Time stamp of Tracking and Filling Runs

  MANDT ACTION REG SCEN START_DATE START_TIME END_DATE END_TIME

  444 FILLING REACH_EU 01.01.2015 00:00:00 11.05.2016 18:56:27

  444 TRACKING REACH_EU EXP 01.01.2016 00:00:00 12.05.2016 15:24:32

  444 TRACKING REACH_EU IMP 26.04.2016 00:00:00 29.04.2016 13:49:54

this is a very important result. So do "filling" and you have scheduled tracknig for "imp" and "exp" only.

But the dates are not "good". filling ended at 11.05. (no riun on 12.05); imp stopped end of april .. pleaase check your job set up

C.B.

PS: Do you run report RREGCH_WL_BUILD and if not why not..? Check

Data Transfer from Property Tree - Product Safety (EHS-SAF) - SAP Library

and look deepere here:

"Schedule report RREGCH_FILL once for initial filling. Then schedule the report in delta mode. We recommend that you schedule the job for the delta run to run every day. If you have set the environment parameter SVT_WL_OFFLINE so that the delta worklist is created offline, schedule program RREGCH_WL_BUILD to run daily also. Schedule the two programs in such a way that program RREGCH_FILL starts in delta mode once program RREGCH_WL-BUILD has finished."

[christoph_bergemann]

Dear Satya

able: CCRCC_PERIOD

Description: EHS: Period Definition

  MANDT PERIOD REG SDAY SMONTH EDAY EMONTH

  444 Q1 REACH_EU 01 01 31 03

  444 Q2 REACH_EU 01 04 30 06

  444 Q3 REACH_EU 01 07 30 09

  444 Q4 REACH_EU 01 10 31 12

Table: CCRCC_ERRMAIL

Description: EHS: Specify Recipients for Error Messages

  MANDT REG BUKRS DOCTYPE DOCCAT REG_LEVEL MSGTYPE RECTYPE RECNAME RFCDEST LANGU RECEIVER

  444 REACH_EU DELIVERY B EN EHSCONS

  444 REACH_EU SALES B EN techserv_to@rajgrp.com

=> you should look at this later; not important in the current situation, anything seems to be set up "ok"

C.B.

[christoph_bergemann]

Dear Satya

conclusion: you used the SAP standard report and showed your customizing set up. Only in one area there is clear wrong set up done (refer to my answers). The "heart" core pieces: we can not judge... (e.g. filter criteria) as this is always company specific

PLease correct the one customizing as this as wll is a "critical" piece in the game

C.B.

[christoph_bergemann]

Dear Saty

coming back to your sentence:

"Next thing when i entered  CBRC20 given regulation as REACH and executed(witch out giving scenario) it is automatically showing the IMP scenario for Purchase and Purchase quantity is automatically updated ....now i need to change monitored values to EXP and delivery scenario which configuration i need to do for that or shall i maintain any environmental parameters for that."

a.) you used cbrc20 correct

b.) youget resutl. Result seems only to be linked to "IMP" scenario

Not knowing your "jobset up" etc. a.) either there is no job running for "PRO" or "EXP" scenrio, or there is no data identfied to selectd and to presnet etc. => check the related SVT tables for "EXP" and "PRO". If they are "empty" then CBRC20 can not show something; to identify reason: this is different story

In contrast to WWI situation in SVT you can "debug" "easyily" and understand the flow of the process. You should be able (with helpof ABAPer) to detect at whcih place teh data is "skipped" (butt you assume ti should show up etc.)

The "filter criteria" you are discussing are the " core cor core"  set up of EHS. If this set up is "wrong" then you will not get result

[satya11719]

Hi,

i understood the concept is there any chance that SAP give function modules are not working properly cause i maintain all the things according to configuration documenst and master data also in place still im not getting required output.

Thanks

Satya

[christoph_bergemann]

Dear Sataya

i can confirm that SAP EHS SVT is working for EXP scenario.

Let us assume now something:

If you use the "SALES" part of EXP scenario and you have prepared corresponding master data correct and any job is running as needed and you have generated a "sales order" the first effect must be:: iF sales order is relevant for EXP and material is relevant you must find some entries in corresponding SVT tables. PLease check this. Reason: Sometimes, if you do not set up correct "access rights" you can not display the data in CBRC20

If you do not find data in the SVT tables then please check CBRC10.

E.g. you have prepared anything correct and started fo rthe frist time EXP on 01.04.2016  then use in the selection screen data 01.04.2016 up to "current date"; subselect the scenario "TRACKING". CHeck if you find something there (and explain/show what you have found)

Check as well in CBRC10 the same but with subscenario "FILLING". Check if you can find log entries of many kind. Of interest is any message of type "warning" or "Error" (Infos you can ignore)

As for DELIVERY part the same SVT "core" tables as for SALES are used you should be as well able to "detect" something

If you have done a "posting" (good movement) for some relevant logistic documents then as well some data should be available in the second SVT core table. Any tables are described in SVT OSS note; therefore I don'T list them

If you can not find anything: check the data of the "sales order" or "delivery" (this is related to your screen; topic of LIKP; LIPS etc.). Make sure that the documents completely fulfill the selection criterias

PLease check the "job logs". For normal companies the run time should be as:

IMP is the fastest part, then production, EXP is the slowest part; but may be you find something in the joblogs..

C.B.

Only for information: later on

report RREGCH_EVALUATE_QUANTITIES

and

RREGCH_EVALUATION

is a good help for analysing SVT topics

PPS: please help why i'm getting IMP scenario in CBRC20 as default and how can i change that to EXP

If you use CBRC20 without scenario you should gte "IMP", "PROD", "EXP" data. As you do not get anything else as "IMP" => conclusion: set up is wrong or no SVT relevant data is present

[christoph_bergemann]

Dear Satya

any update here?

C.B.