VOFM routines activation

Hi Sap Guru's,
As per my client requirement, I have maintained new routine in VOFM by using below navigation:
routine names are 902 & 903 & their includes are RV64A902 & RV64A903.
Now, when we move the changes to quality server then the routines are showing in VOFM but in standard program RV64ANNN it’s not
available. (so when we run sales order then the includes 902 & 903 is not triggering)
So I ran the standard program RV80HGEN. (to activate VOFM routines)
Then the routine names are populated into standard program RV64ANNN. (when we run sales order then the includes 902 & 903 is triggering & its working as expected)
But same changes we moved to production server, so if I will run the same standard program RV80HGEN in production environment then all other
customized routines also activating including my 902 & 903 routines.
So please suggest me, how can I will overcome the situation.
I have to activate my routines 902 & 903 only in production server.
Thanks in advance.
BR,
Shabareesh

Hello,
but still I don't understand your perplexity:
In order to avoid all confusions, we have planned to do below steps:
Capture our routines in new TR with standard program RV64ANNN (Development server)
Then we will move the changes to QAS server & check the result
If result would be fine, then we will move the TR to PRD.
this should be the standard and "best-practice" approach for any kind of change.
Request you to confirm on above point or we will go ahead to run RV80HGEN program directly in PRD.
When you transport a newly created routine, you always need to run program RV80HGEN to be sure that it's correctly and completely activated. But it won't do any harm. Unless you moved to Production environment a routine that you don't want to activate: but this is not the correct and advisable approach.
Best regards,
Andrea

Similar Messages

Activating a VOFM Routine

Hi Folks,
I have made a VOFM routine in data tranfer->Sales activities.I have activated the program and also the entry in "Maintain:Data transport sales activities" But still i am getting an error "No frame work was found for the Include RV44A601".I have no idea which configuration is missing now please help.I have also tried using SAP program RV80HGEN first and then Standard SAP program SDINVOFM used to identify and repair missing table entries in the VOFM control tables TFRM and TFRMT but in vain..:(
Attached are the screenshots.
Error:
Activated Program and Entry:
Thanks in Advance.

Abhishek,
There is no need to activate the standard programs like SAPLV43A or RV**NNN program separately when you are creating a custom routine.Once you register the Custom Routine in SAP Service Market Place you will get the SCCR key so that you can proceed with the coding.Once the coding you can activate the routine using RV80HGEN.This will activate the routine.To cross check whether the routine has got activated or not you can check if there is an entry with your custom routine program name in the corresponding RV**NNN program.This is only for confirmation and there is no need to separately activate other standard programs or transport these program along with your custom routine.
Running RV80HGEN will take care of activating the routine.The same activity needs to be done again once the TR is imported in the target client.
If you want to run RV80HGEN automatically ( instead of performing it as a cut over activity once the TR is imported to target client ) you can tag RV80HGEN as XPRA along with your custom routine in the TR and get this imported to target client.XPRA will set RV80HGEN for execution once the TR is imported to the target client.
You can refer to SAP Notes 86161 and 327220 for more info.
K.Kiran.

Vofm routines

hi iam doing an vofm routine in which i have to create an routine under FORMULAS
-> CONDITION BASE VALUE!!
the objective of my enhancemnet is to reduce installl price by the value of the measure!! can u plss explain this!!!wat does this mean.
n also wid the code!!!!

Hi
VOFM is the transaction where you can maintain Requirement routines, which are assigned through cusomization.
To create a routine you need access key & routine no. starts with "9".for ex. 901,902 etc.
one important thing to note that even if you have some syntax errors inside your routine, it will get activated without errors. So, you need to do Main Program check before activation.
Refer to SAP Note no : 327220,381348,156230.
So create a routine above 900 and copy the similar existing routine with code and do your changes as per your requirement.
<b>
Reward points for useful Answers</b>
Regards
Anji

How can I actiave a VOFM routine

I m in VOFM TCode. I have an existing routine. But the Active checkbox in front of that routine is unchecked. Also this checkbox is not editable from VOFM. How can I make this routine active.
Thanks for reading. <REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Mar 28, 2008 7:29 PM

are you sure you are in the right forum ?
This is for Business Objects product and your question make no sense in that context

Field symbols not working in data transfer VOFM routine

Hi,
I have been trying to set a value using field symbols, however for some reasons its not working. I am using a field symbol in a data transfer routine and the value which I am trying to set is a standard field outside the VOFM routine code.
I am trying to set a field gla_subrc which is actually a changing parameter.
The actual paramter is gn_subrc of type sy-subrc and within the form the name is gla_subrc. I need to set this changing parameter gla_subrc using the data transfer routine.
Is there a specific rule that field symbols dont work for changing paramters within subroutine or is there a specific syntax.
The syntax I am using is
ASSIGN ('(SAPLV50S)gla_subrc') to <fs>.
I also used the local program name instead of main program but still that does not work. Tried using the actual parameter as well.
Can someone please help me in this.
Thanks & Regards,
Naresh.

I need to stop outbound delivery creation against STO using vl10b transaction. The only way to stop creation is using data transfer delivery VOFM routine.
If i give an error message MESSAGE E001, this will give a hard error which is not acceptable. To avoid this, i use a perform message statment with message id and certain parameters which can displayed in a log.
However to make sure this message is displayed in log, I am clearing a work area having specific data needed for delivery creation.
Because of this clear, my error message gets captured in log but along with this another fake message is displayed in log which caused by the clear message.
The user gets confused as he now sees 2 messages, 1 which is correct and other 1 which is fake and that confuses him.
Data transfer routine is not the best place to give messages in log but we have very few options. The only way the system can give 1 message is if i set gla_subrc to 1. This is a variable which will help the system understand that the delivery should not be created as there is something wrong because the value is 1. Hence it will stop the creation and instead display whatever message i had passed to the log.
I need to somehow set this variable to 1 based on lot of analysis that has been done in the past.
Please let me know if there is any way by which we can fix this.
Thanks & Regards,
Naresh.

How to restrict issue the form through VOFM routine

Hi Experts,
I have developed form using adobe form, I need to issue the output only one time, once the output issued again the output should not issue.
I need to control this logic through VOFM routine...how to restrict ?
Thanks in advance.

Srinath,
Use the below option.
VOFM->REQUIREMENTS->O?P Control.
Create a new routine.
In the routine, check the table NAST using application, object key and message type. If you find an entry, set the sy-subrc value to 4 else set the subrc value to 0.
Let me know if this helps.
Thanks,
Vikram.M

VOFM Routine Copy in ECC 6.0

Hi,
When I copy a VOFM routine in ECC 6.0 (say billing document routine 001 copied to 901) to a custom routine, I see some messages regarding the existing enahancement points & sections, which do not allow me to activate the copied routine. Can any one of you suggest a good practice to copy the routine in ECC 6.0 environment.
Thanks
BK

Hi,
When ever you are copying it from the standard routine. The enhancement points and sections available in the standard will also be copied into the custom. So, Place the cursor on Enhancement-pont or Enhancement-section and right click select the option enhancement-> undo. Once you do this the enhancements will be deleted from custom routine and then you can activate it.
Thanks
Indira.

VK11 condition check against MEK1 conditions: VOFM routins or UserExit/BADI

We have Z condition types for prices(SD side)..and some Z condition types for Costs (MM side). My requirement is to check costs assosciated with the Material based on MM condition types when creating SD prices (condition records) and do vice versa and throw information/warning/error messages...
In otherwords...when creating condition records from VK11 check against costs that are created in MEK1 and Vice Versa.
I am trying to accomplish this in VOFM routines partially if not fully.
Can this be achieved through VOFM routines.
If VOFM is not the right place..what is the correct UE/BADI for this.
Thanks.

You already received an answer on this yesterday in a different post - why the new post?
That aside, you don't understand the purpose of a requirement against an access in an access sequence. The requirement prevents the access from being triggered (or allows it) at the time that the line item condition is analyzed for pricing (during the creation of an order/contract/etc.). If the access is prevented, then the existing condition records for the access are never analyzed for a match. It has nothing to do with condition record entry in VK11. If you need to change the behavior of VK11, then use Runtime Analysis to check for BADI's or enhancement points in the transaction by analyzing the call stack.

VOFM, RV45C901 Activation

Hi all,
I've created a custom data transfer routine (RV45C901). The problem is I get a short dump in our production system whenever I try to run it. We encountered this in QA and I reactivated a bunch of stuff (I don't remember what order and what objects) but eventually got it to work.
In our production box I was going to try to deactivate and reactivate it in VOFM but it has status "not modifiable". So in development I created a new transport where I deactivated and reactivated the routine in VOFM. This still didn't work.
Any ideas? Are there specific steps to take? How can this be avoided in the future?
Thanks!

Hi,
Try to run the program RV80HGEN to generate the VOFM routines..
In future when you are transporting the VOFM routine..Manually add a entry in the CR with the following data in the object list..
R3TR XPRA RV80HGEN
If you give this the program RV80HGEN will run once the transport is complete..
Hope this helps..
Thanks,
Naren

Why SAP has provided the VOFM routines even though we do have User-Exits?

Hi Experts,
Pls. let me clarify about,
1) What is the difference between VOFM routines and User-Exits?
2) Why SAP has provided the VOFM routines, even though we are having User-Exits, BADIs?
3) Is VOFM is meant for only SD module or we also use VOFM in other modules too, like MM, PP?
thanq

Do be careful about asking questions that sound like interview questions...
> 1) What is the difference between VOFM routines and User-Exits?
VOFM are type of user exit.
>
> 2) Why SAP has provided the VOFM routines, even though we are having User-Exits, BADIs?
>
Historical. They were created before BADIs and CMOD user exits were invented. The other "old" user exits in SD are the user exit forms.
> 3) Is VOFM is meant for only SD module or we also use VOFM in other modules too, like MM, PP?
>
Only SD.
> thanq
You're welcome.

How to test VOFM routine for output cntrol-issue o/p when certain conds met

Hai,
I have created a vofm routine 903 for the output type 'ZSH1'.This is for sales order output.
The 903 routine changes the sy-subrc value to non zero if certain conditions met.
My doubt is how to test this vofm routine? where can we check the status of the output processed?
This output is to trigger a smartform.
In my case the output smart form got displayed when I click on print preview even if the condtions met (or) dont met.
Is this the correct way of testing?
Regards,
Bhaskar

Hai All,
Thanks for your replies.
here my question is,
how to test the VOFM (not manual )& where we can check the status of output issued or not issued?
see the step 1.
Step1: goto->va02->from the menu select 'issue output'->select the codition type in the displayed popup->click OK.
after this where can I check the status of the output issued?
or is the way I described in Step 1 is correct or not ?
other way Step 2:
goto VA02->enter order number->goto overview page->from Extras->output->header->edit
in this page maintain the output type & click Save.
after Save , is this the time to check whether the output issued or not? if yes where to check the status?
or again is this the right way to test the VOFM.
Regards,
Bhaskar
Edited by: Mbhaskar_comps on Dec 15, 2010 7:00 AM

Vofm fomula routin activation error.

i have complete a formula via tc:'VOFM', and i would like to active the routin, but get error message" Report/Program statement missing, or program type is i (include)". what can i do?

Hi,
You have to create the routine via VOFM, an include will automatically be created in the required main include/program. Put you your codes in the routine/form activate it. then got back to VOFM :
- select routine
- Click on EDIT and activate
This will activate your codes and routine.
Regrads,
Dev.

VOFM routine - NO frame work

Hi all,
    By posting an inbound idoc we are creatin a purchase order and post goods issue for the purchase order.
    When a purchase order is getting created an entry is getting updated in NAST table which trigger the idoc ORDERS05.
    This idoc triggering should happen only when the Post goods issue is successful.
    Now for this am creating a routine in vofm. 903. Inside the routine am looping at XNAST table and checking for condition
    and making the sy-subrc as 4. i activated the include and routine. i executed the program RV80HGEN.
    But when i try to create a break point there it says.."No framework program was found for include RV61B903"
This routine is related with output Control...kindly help..
   What am I doing wrong here.
   Regards
   Sridevi S
Edited by: Sridevi Sivanandam on Jan 7, 2011 7:45 AM
Edited by: Sridevi Sivanandam on Jan 7, 2011 7:47 AM

You can try testing this by:
- assign your output type and put there dispatch time = '1'
- setup breakpoint
- execute program RSNAST00 for your PO/output type
This way you should be able to debug output triggering.
Regards,
Dominik Modrzejewski

0IC_C03: 2LIS_03_BF Transformation Start Routine Activation error

Hi all,
Iam getting activation error (Start Routine) while activating the transformation for the 2LIS_03_BF (Material Movements) data source for 0IC_C03 INFO CUBE. Iam getting an error for the Start Routine and the error message is as follows:
+ E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter "SOURCE_PACKAGE" is incompatible with the formal parameter "DATA_PACKAGE".+
Scenario: As per my client requirment i have tried to add on info object in to the existing info cube i.e., Movement Type which is an existing field in the info source and the data source and i have tried to map the same in the transformations between the info source and the info cube and activated the transformation. Then iam getting the above said start routine error, so to avoid this i have removed that object i.e., movement type from the info cube and tried to reactivate the transformations still iam getting the same routine error.
Please suggest me th approach to resolve this issue.
Regards,
Prabhakar

Hi Chandu,
Please find below is the routine:
PROGRAM trans_routine.
      CLASS routine DEFINITION
CLASS lcl_transform DEFINITION.
PUBLIC SECTION.
Attributs
    DATA:
      p_check_master_data_exist
            TYPE RSODSOCHECKONLY READ-ONLY,
*-    Instance for getting request runtime attributs;
    Available information: Refer to methods of
    interface 'if_rsbk_request_admintab_view'
      p_r_request
            TYPE REF TO if_rsbk_request_admintab_view READ-ONLY.
PRIVATE SECTION.
    TYPE-POOLS: rsd, rstr.
Rule specific types
    TYPES:
      BEGIN OF tys_SC_1,
     InfoObject: 0STORNO Reversal Indicator.
        STORNO           TYPE /BI0/OISTORNO,
     InfoObject: 0RT_PROMO promotion.
        RT_PROMO           TYPE /BI0/OIRT_PROMO,
     InfoObject: 0VAL_CLASS Valuation class.
        VAL_CLASS           TYPE /BI0/OIVAL_CLASS,
     InfoObject: 0DOC_DATE Document Date.
        DOC_DATE           TYPE /BI0/OIDOC_DATE,
     InfoObject: 0STOCKTYPE StockType.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0STOCKCAT Stock Categories.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0PSTNG_DATE Posting date in the document.
        PSTNG_DATE           TYPE /BI0/OIPSTNG_DATE,
     InfoObject: 0COMP_CODE Company Code.
        COMP_CODE           TYPE /BI0/OICOMP_CODE,
     InfoObject: 0BWAPPLNM Application component.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0MOVETYPE movement Type (Inventory Management).
        MOVETYPE           TYPE /BI0/OIMOVETYPE,
     InfoObject: 0STOCKRELEV BW: Relevance to Stock.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0CPPVLC BW: Purchase Value in Local currency.
        CPPVLC           TYPE /BI0/OICPPVLC,
     InfoObject: 0CPSVLC BW: Sales Value in Local currency.
        CPSVLC           TYPE /BI0/OICPSVLC,
     InfoObject: 0CPSTLC BW: Sales Value in Local currency.
        CPSTLC           TYPE /BI0/OICPSTLC,
     InfoObject: 0CPQUABU BW: Amount in base unit of Measure.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0VAL_TYPE Valuation Type.
        VAL_TYPE           TYPE /BI0/OIVAL_TYPE,
     InfoObject: 0PROCESSKEY BW: Transaction Key.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0BATCH Batch number.
        BATCH           TYPE /BI0/OIBATCH,
     InfoObject: 0MATMREA Reason for Goods Movement.
        MATMREA           TYPE /BI0/OIMATMREA,
     InfoObject: 0BUS_AREA Business Area.
        BUS_AREA           TYPE /BI0/OIBUS_AREA,
     InfoObject: 0COSTCENTER Cost Center.
        COSTCENTER           TYPE /BI0/OICOSTCENTER,
     InfoObject: 0SOLD_TO Sold-to Party.
        SOLD_TO           TYPE /BI0/OISOLD_TO,
     InfoObject: 0WHSE_NUM Warehouse Number / warehouse complex.
        WHSE_NUM           TYPE /BI0/OIWHSE_NUM,
     InfoObject: 0STOR_LOC Storage Location.
        STOR_LOC           TYPE /BI0/OISTOR_LOC,
     InfoObject: 0STRGE_BIN Storage Bin.
        STRGE_BIN           TYPE /BI0/OISTRGE_BIN,
     InfoObject: 0STRGE_TYPE Storage Type.
        STRGE_TYPE           TYPE /BI0/OISTRGE_TYPE,
     InfoObject: 0VENDOR Vendor.
        VENDOR           TYPE /BI0/OIVENDOR,
     InfoObject: 0MATERIAL Material.
        MATERIAL           TYPE /BI0/OIMATERIAL,
     InfoObject: 0DOC_NUM BW: Document Number.
        DOC_NUM           TYPE /BI0/OIDOC_NUM,
     InfoObject: 0BASE_UOM Base Unit of Measure.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
     InfoObject: 0DOC_YEAR BW: Document Year.
        DOC_YEAR           TYPE /BI0/OIDOC_YEAR,
     InfoObject: 0PROFIT_CTR Profit center.
        PROFIT_CTR           TYPE /BI0/OIPROFIT_CTR,
     InfoObject: 0DCINDIC Debit/Credit Indicator.
        DCINDIC           TYPE /BI0/OIDCINDIC,
     InfoObject: 0LOC_CURRCY Local currency.
        LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
     InfoObject: 0PLANT Plant.
        PLANT           TYPE /BI0/OIPLANT,
     InfoObject: 0FISCVARNT Fiscal year variant.
        FISCVARNT           TYPE /BI0/OIFISCVARNT,
     InfoObject: 0CPNOITEMS BW: Number of activities.
        CPNOITEMS           TYPE /BI0/OICPNOITEMS,
     InfoObject: 0CO_AREA Controlling Area.
        CO_AREA           TYPE /BI0/OICO_AREA,
     InfoObject: 0DOC_ITEM BW: Document Line Number.
        DOC_ITEM           TYPE /BI0/OIDOC_ITEM,
     InfoObject: 0VALUE_LC Amount in local currency.
        VALUE_LC           TYPE /BI0/OIVALUE_LC,
     InfoObject: 0QUANT_B Quantity in base units of Measure.
        QUANT_B           TYPE /BI0/OIQUANT_B,
     InfoObject: 0MOVE_PLANT Receiving Plant/Issuing Plant.
        MOVE_PLANT           TYPE /BI0/OIMOVE_PLANT,
     InfoObject: 0RECORDMODE BW Delta Process: Update Mode.
        RECORDMODE           TYPE RODMUPDMOD,
     InfoObject: 0RT_RMAPIDA RMA Physical Inventory Date.
        RT_RMAPIDA           TYPE /BI0/OIRT_RMAPIDA,
     InfoObject: 0BWCOUNTER Additional Key Field Revaluation Document
*Record.
        BWCOUNTER           TYPE /BI0/OIBWCOUNTER,
     InfoObject: 0INDSPECSTK Indicator: Valuation of Special stock.
        INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
     InfoObject: 0GN_R3_SSY Source System for R/3 Entity.
        GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
     InfoObject: 0RT_MOVINV movement Type is Physical Inventory.
        RT_MOVINV           TYPE /BI0/OIRT_MOVINV,
     InfoObject: 0RT_MOVADJ movement Type is Stock Adjustment.
        RT_MOVADJ           TYPE /BI0/OIRT_MOVADJ,
     InfoObject: 0RSL_STMAT Structured Article.
        RSL_STMAT           TYPE /BI0/OIRSL_STMAT,
     InfoObject: 0RT_MOVRET movement Type is Return.
        RT_MOVRET           TYPE /BI0/OIRT_MOVRET,
     InfoObject: 0RSL_STAUTO Automatically Completed Component.
        RSL_STAUTO           TYPE /BI0/OIRSL_STAUTO,
     InfoObject: 0RT_MOVTRAN movement Type is Stock Transfer.
        RT_MOVTRAN           TYPE /BI0/OIRT_MOVTRAN,
     InfoObject: 0RT_MATPOST Transfer Posting from Article to Article
        RT_MATPOST           TYPE /BI0/OIRT_MATPOST,
     InfoObject: 0RT_SASTSV Share of Business Volume for Set Sales Val
*ue in Local crcy.
        RT_SASTSV           TYPE /BI0/OIRT_SASTSV,
     InfoObject: 0RT_SASTST Share of Business Volume for Set with Tax
*in Local currency.
        RT_SASTST           TYPE /BI0/OIRT_SASTST,
     InfoObject: 0COORDER order number.
        COORDER           TYPE /BI0/OICOORDER,
     InfoObject: 0RMA_LNK RMA Stock Transfer Reference Item.
        RMA_LNK           TYPE /BI0/OIRMA_LNK,
     InfoObject: 0RMA_RFLG RMA Relevance Flag.
        RMA_RFLG           TYPE /BI0/OIRMA_RFLG,
     InfoObject: 0RTHFEES Stock Transfer Fees.
        RTHFEES           TYPE /BI0/OIRTHFEES,
     Field: RECORD.
        RECORD           TYPE RSARECORD,
      END   OF tys_SC_1.
    TYPES:
tyt_SC_1        TYPE STANDARD TABLE OF tys_SC_1
                        WITH NON-UNIQUE DEFAULT KEY.
$$ begin of global - insert your declaration only below this line -
... "insert your code here
$$ end of global - insert your declaration only before this line   -
    METHODS
      start_routine
        IMPORTING
          request                  type rsrequest
          datapackid               type rsdatapid
        EXPORTING
          monitor                  type rstr_ty_t_monitors
        CHANGING
          SOURCE_PACKAGE              type tyt_SC_1
        RAISING
          cx_rsrout_abort.
    METHODS
      inverse_start_routine
        IMPORTING
          i_th_fields_outbound         TYPE rstran_t_field_inv
          i_r_selset_outbound          TYPE REF TO cl_rsmds_set
          i_is_main_selection          TYPE rs_bool
          i_r_selset_outbound_complete TYPE REF TO cl_rsmds_set
          i_r_universe_inbound         TYPE REF TO cl_rsmds_universe
        CHANGING
          c_th_fields_inbound          TYPE rstran_t_field_inv
          c_r_selset_inbound           TYPE REF TO cl_rsmds_set
          c_exact                      TYPE rs_bool.
ENDCLASS.                    "routine DEFINITION
$$ begin of 2nd part global - insert your code only below this line *
    TYPES:
      BEGIN OF tys_SC_1_full,
     InfoObject: 0STORNO Stornokennzeichen.
        STORNO           TYPE /BI0/OISTORNO,
     InfoObject: 0RT_PROMO Aktion.
        RT_PROMO           TYPE /BI0/OIRT_PROMO,
     InfoObject: 0VAL_CLASS Bewertungsklasse.
        VAL_CLASS           TYPE /BI0/OIVAL_CLASS,
     InfoObject: 0DOC_DATE Belegdatum.
        DOC_DATE           TYPE /BI0/OIDOC_DATE,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0PSTNG_DATE Buchungsdatum im Beleg.
        PSTNG_DATE           TYPE /BI0/OIPSTNG_DATE,
     InfoObject: 0COMP_CODE Buchungskreis.
        COMP_CODE           TYPE /BI0/OICOMP_CODE,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0MOVETYPE Bewegungsart (Bestandsführung).
        MOVETYPE           TYPE /BI0/OIMOVETYPE,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
        CPPVLC           TYPE /BI0/OICPPVLC,
     InfoObject: 0CPSVLC BW: Verkaufswert in Hauswährung.
        CPSVLC           TYPE /BI0/OICPSVLC,
     InfoObject: 0CPSTLC BW: VerkWmS Hauswährung.
        CPSTLC           TYPE /BI0/OICPSTLC,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0VAL_TYPE Bewertungsart.
        VAL_TYPE           TYPE /BI0/OIVAL_TYPE,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0BATCH Chargennummer.
        BATCH           TYPE /BI0/OIBATCH,
     InfoObject: 0MATMREA Grund für die Warenbewegung.
        MATMREA           TYPE /BI0/OIMATMREA,
     InfoObject: 0BUS_AREA Geschäftsbereich.
        BUS_AREA           TYPE /BI0/OIBUS_AREA,
     InfoObject: 0COSTCENTER Kostenstelle.
        COSTCENTER           TYPE /BI0/OICOSTCENTER,
     InfoObject: 0SOLD_TO Auftraggeber.
        SOLD_TO           TYPE /BI0/OISOLD_TO,
     InfoObject: 0WHSE_NUM Lagernummer/Lagerkomplex.
        WHSE_NUM           TYPE /BI0/OIWHSE_NUM,
     InfoObject: 0STOR_LOC Lagerort.
        STOR_LOC           TYPE /BI0/OISTOR_LOC,
     InfoObject: 0STRGE_BIN Lagerplatz.
        STRGE_BIN           TYPE /BI0/OISTRGE_BIN,
     InfoObject: 0STRGE_TYPE Lagertyp.
        STRGE_TYPE           TYPE /BI0/OISTRGE_TYPE,
     InfoObject: 0VENDOR Lieferant.
        VENDOR           TYPE /BI0/OIVENDOR,
     InfoObject: 0MATERIAL Material.
        MATERIAL           TYPE /BI0/OIMATERIAL,
     InfoObject: 0DOC_NUM BW: Belegnummer.
        DOC_NUM           TYPE /BI0/OIDOC_NUM,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
     InfoObject: 0DOC_YEAR BW: Belegjahr.
        DOC_YEAR           TYPE /BI0/OIDOC_YEAR,
     InfoObject: 0PROFIT_CTR Profit Center.
        PROFIT_CTR           TYPE /BI0/OIPROFIT_CTR,
     InfoObject: 0DCINDIC Soll-/Haben-Kennzeichen.
        DCINDIC           TYPE /BI0/OIDCINDIC,
     InfoObject: 0LOC_CURRCY Hauswährung.
        LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
     InfoObject: 0PLANT Werk.
        PLANT           TYPE /BI0/OIPLANT,
     InfoObject: 0FISCVARNT Geschäftsjahresvariante.
        FISCVARNT           TYPE /BI0/OIFISCVARNT,
     InfoObject: 0CPNOITEMS BW: Anzahl Vorgänge.
        CPNOITEMS           TYPE /BI0/OICPNOITEMS,
     InfoObject: 0CO_AREA Kostenrechnungskreis.
        CO_AREA           TYPE /BI0/OICO_AREA,
     InfoObject: 0DOC_ITEM BW: Belegpositionsnummer.
        DOC_ITEM           TYPE /BI0/OIDOC_ITEM,
     InfoObject: 0VALUE_LC Betrag in Hauswährung.
        VALUE_LC           TYPE /BI0/OIVALUE_LC,
     InfoObject: 0COORDER Auftragsnummer.
        COORDER           TYPE /BI0/OICOORDER,
     InfoObject: 0QUANT_B Menge in Basismengeneinheiten.
        QUANT_B           TYPE /BI0/OIQUANT_B,
     InfoObject: 0MOVE_PLANT Empfangendes/Abgebendes Werk.
        MOVE_PLANT           TYPE /BI0/OIMOVE_PLANT,
     InfoObject: 0RECORDMODE BW Deltaverfahren: Update Modus.
        RECORDMODE           TYPE RODMUPDMOD,
     InfoObject: 0RT_RMAPIDA RMA Inventurdatum.
        RT_RMAPIDA           TYPE /BI0/OIRT_RMAPIDA,
     InfoObject: 0BWCOUNTER Zusätzliches Schlüsselfeld Umbewertungsbel
*egsatz.
        BWCOUNTER           TYPE /BI0/OIBWCOUNTER,
     InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
        INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
     InfoObject: 0GN_R3_SSY Quellsystem der R/3 Entität.
        GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
     InfoObject: 0RT_MOVINV Bewegungsart ist Inventur.
        RT_MOVINV           TYPE /BI0/OIRT_MOVINV,
     InfoObject: 0RT_MOVADJ Bewegungsart ist Bestandskorrektur.
        RT_MOVADJ           TYPE /BI0/OIRT_MOVADJ,
     InfoObject: 0RSL_STMAT Strukturierter Artikel.
        RSL_STMAT           TYPE /BI0/OIRSL_STMAT,
     InfoObject: 0RT_MOVRET Bewegungsart ist Retoure.
        RT_MOVRET           TYPE /BI0/OIRT_MOVRET,
     InfoObject: 0RSL_STAUTO Automatisch ergänzte Komponente.
        RSL_STAUTO           TYPE /BI0/OIRSL_STAUTO,
     InfoObject: 0RT_MOVTRAN Bewegungsart ist Umlagerung.
        RT_MOVTRAN           TYPE /BI0/OIRT_MOVTRAN,
     InfoObject: 0RT_MATPOST Umbuchung Artikel an Artikel.
        RT_MATPOST           TYPE /BI0/OIRT_MATPOST,
     InfoObject: 0RT_SASTSV Umsatzanteil am Set Verkaufswert in Hauswä
*hrung.
        RT_SASTSV           TYPE /BI0/OIRT_SASTSV,
     InfoObject: 0RT_SASTST Umsatzanteil am Set Verkaufswert mit Steue
*r in Hauswährung.
        RT_SASTST           TYPE /BI0/OIRT_SASTST,
     Field: RECORD.
        RECORD           TYPE RSARECORD,      END   OF tys_SC_1_full.
    TYPES:
tyt_SC_1_full        TYPE STANDARD TABLE OF tys_SC_1_full
                        WITH NON-UNIQUE DEFAULT KEY.
    TYPES:
      BEGIN OF tys_TG_1_full,
     InfoObject: 0CHNGID Änderungslauf ID.
        CHNGID           TYPE /BI0/OICHNGID,
     InfoObject: 0RECORDTP Satztyp.
        RECORDTP           TYPE /BI0/OIRECORDTP,
     InfoObject: 0REQUID Request ID.
        REQUID           TYPE /BI0/OIREQUID,
     InfoObject: 0CALDAY Kalendertag.
        CALDAY           TYPE /BI0/OICALDAY,
     InfoObject: 0CALMONTH Kalenderjahr / Monat.
        CALMONTH           TYPE /BI0/OICALMONTH,
     InfoObject: 0CALWEEK Kalenderjahr / Woche.
        CALWEEK           TYPE /BI0/OICALWEEK,
     InfoObject: 0CALYEAR Kalenderjahr.
        CALYEAR           TYPE /BI0/OICALYEAR,
     InfoObject: 0MATERIAL Material.
        MATERIAL           TYPE /BI0/OIMATERIAL,
     InfoObject: 0PLANT Werk.
        PLANT           TYPE /BI0/OIPLANT,
     InfoObject: 0STOR_LOC Lagerort.
        STOR_LOC           TYPE /BI0/OISTOR_LOC,
     InfoObject: 0BATCH Chargennummer.
        BATCH           TYPE /BI0/OIBATCH,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0GN_VENDOR Lieferant.
        GN_VENDOR           TYPE /BI0/OIGN_VENDOR,
     InfoObject: 0RECVS_VAL Zugangswert Bewerteter Bestand.
        RECVS_VAL           TYPE /BI0/OIRECVS_VAL,
     InfoObject: 0ISSVS_VAL Abgangswert Bewerteter Bestand.
        ISSVS_VAL           TYPE /BI0/OIISSVS_VAL,
     InfoObject: 0ISSBLOSTCK Abgangsmenge Gesperrter Bestand.
        ISSBLOSTCK           TYPE /BI0/OIISSBLOSTCK,
     InfoObject: 0ISSCNSSTCK Abgangsmenge Konsignationsbestand.
        ISSCNSSTCK           TYPE /BI0/OIISSCNSSTCK,
     InfoObject: 0ISSQMSTCK Abgangsmenge Qualitätsbestand.
        ISSQMSTCK           TYPE /BI0/OIISSQMSTCK,
     InfoObject: 0ISSTRANSST Abgangsmenge Transitbestand.
        ISSTRANSST           TYPE /BI0/OIISSTRANSST,
     InfoObject: 0RECBLOSTCK Zugangsmenge Gesperrter Bestand.
        RECBLOSTCK           TYPE /BI0/OIRECBLOSTCK,
     InfoObject: 0RECCNSSTCK Zugangsmenge Konsignationsbestand.
        RECCNSSTCK           TYPE /BI0/OIRECCNSSTCK,
     InfoObject: 0RECQMSTCK Zugangsmenge Qualitätsbestand.
        RECQMSTCK           TYPE /BI0/OIRECQMSTCK,
     InfoObject: 0RECTRANSST Zugangsmenge Transitbestand.
        RECTRANSST           TYPE /BI0/OIRECTRANSST,
     InfoObject: 0ISSSCRP Abgangsmenge Ausschuss.
        ISSSCRP           TYPE /BI0/OIISSSCRP,
     InfoObject: 0ISSVALSCRP Abgangswert Ausschuss.
        ISSVALSCRP           TYPE /BI0/OIISSVALSCRP,
     InfoObject: 0RECTOTSTCK Zugangsmenge Gesamt Bestand.
        RECTOTSTCK           TYPE /BI0/OIRECTOTSTCK,
     InfoObject: 0ISSTOTSTCK Abgangsmenge Gesamtbestand.
        ISSTOTSTCK           TYPE /BI0/OIISSTOTSTCK,
     InfoObject: 0ISSVALSTCK Abgangsmenge Bewerteter Bestand.
        ISSVALSTCK           TYPE /BI0/OIISSVALSTCK,
     InfoObject: 0RECVALSTCK Zugangsmenge Bewerteter Bestand.
        RECVALSTCK           TYPE /BI0/OIRECVALSTCK,
     InfoObject: 0VENCONCON Verbrauchswerte Lieferantenkonsignationsbe
*stand.
        VENCONCON           TYPE /BI0/OIVENCONCON,
     InfoObject: 0LOC_CURRCY Hauswährung.
        LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
     Field: RECORD Nummer des Datensatzes.
        RECORD           TYPE RSARECORD,
      END   OF tys_TG_1_full.
    TYPES:
      BEGIN OF tys_SC_1__RULE_9,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_9.
    TYPES:
      BEGIN OF tys_SC_1__RULE_10,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_10.
    TYPES:
      BEGIN OF tys_SC_1__RULE_11,
     InfoObject: 0GN_R3_SSY Quellsystem der R/3 Entität.
        GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0VENDOR Lieferant.
        VENDOR           TYPE /BI0/OIVENDOR,
      END   OF tys_SC_1__RULE_11.
    TYPES:
      BEGIN OF tys_SC_1__RULE_12,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
        CPPVLC           TYPE /BI0/OICPPVLC,
     InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
        INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0LOC_CURRCY Hauswährung.
        LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
      END   OF tys_SC_1__RULE_12.
    TYPES:
      BEGIN OF tys_SC_1__RULE_13,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
        CPPVLC           TYPE /BI0/OICPPVLC,
     InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
        INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0LOC_CURRCY Hauswährung.
        LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
      END   OF tys_SC_1__RULE_13.
    TYPES:
      BEGIN OF tys_SC_1__RULE_15,
     InfoObject: 0GN_R3_SSY Quellsystem der R/3 Entität.
        GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0VENDOR Lieferant.
        VENDOR           TYPE /BI0/OIVENDOR,
      END   OF tys_SC_1__RULE_15.
    TYPES:
      BEGIN OF tys_SC_1__RULE_19,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_19.
    TYPES:
      BEGIN OF tys_SC_1__RULE_20,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_20.
    TYPES:
      BEGIN OF tys_SC_1__RULE_21,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
        INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_21.
    TYPES:
      BEGIN OF tys_SC_1__RULE_22,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0INDSPECSTK Kennzeichen Bewertung Sonderbestand.
        INDSPECSTK           TYPE /BI0/OIINDSPECSTK,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_22.
    TYPES:
      BEGIN OF tys_SC_1__RULE_25,
     InfoObject: 0GN_R3_SSY Quellsystem der R/3 Entität.
        GN_R3_SSY           TYPE /BI0/OIGN_R3_SSY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0VENDOR Lieferant.
        VENDOR           TYPE /BI0/OIVENDOR,
      END   OF tys_SC_1__RULE_25.
    TYPES:
      BEGIN OF tys_SC_1__RULE_31,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
        CPPVLC           TYPE /BI0/OICPPVLC,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0LOC_CURRCY Hauswährung.
        LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
      END   OF tys_SC_1__RULE_31.
    TYPES:
      BEGIN OF tys_SC_1__RULE_37,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_37.
    TYPES:
      BEGIN OF tys_SC_1__RULE_38,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_38.
    TYPES:
      BEGIN OF tys_SC_1__RULE_39,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_39.
    TYPES:
      BEGIN OF tys_SC_1__RULE_40,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_40.
    TYPES:
      BEGIN OF tys_SC_1__RULE_41,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKCAT Bestandstypen.
        STOCKCAT           TYPE /BI0/OISTOCKCAT,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_41.
    TYPES:
      BEGIN OF tys_SC_1__RULE_42,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0PROCESSKEY BW:Vorgangsschlüssel.
        PROCESSKEY           TYPE /BI0/OIPROCESSKEY,
     InfoObject: 0STOCKRELEV BW: Best.Relevanz.
        STOCKRELEV           TYPE /BI0/OISTOCKRELEV,
     InfoObject: 0STOCKTYPE Bestandsausprägung.
        STOCKTYPE           TYPE /BI0/OISTOCKTYPE,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_42.
    TYPES:
      BEGIN OF tys_SC_1__RULE_43,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPQUABU BW: Menge in Basismengeneinheit.
        CPQUABU           TYPE /BI0/OICPQUABU,
     InfoObject: 0MOVETYPE Bewegungsart (Bestandsführung).
        MOVETYPE           TYPE /BI0/OIMOVETYPE,
     InfoObject: 0BASE_UOM Basismengeneinheit.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
      END   OF tys_SC_1__RULE_43.
    TYPES:
      BEGIN OF tys_SC_1__RULE_51,
     InfoObject: 0BWAPPLNM Anwendungskomponente.
        BWAPPLNM           TYPE /BI0/OIBWAPPLNM,
     InfoObject: 0CPPVLC BW: Einkaufswert in Hauswährung.
        CPPVLC           TYPE /BI0/OICPPVLC,
     InfoObject: 0MOVETYPE Bewegungsart (Bestandsführung).
        MOVETYPE           TYPE /BI0/OIMOVETYPE,
     InfoObject: 0LOC_CURRCY Hauswährung.
        LOC_CURRCY           TYPE /BI0/OILOC_CURRCY,
      END   OF tys_SC_1__RULE_51.
Additional types for start routine interface
TYPES:
    data_package_structure type tys_SC_1_full.
Additional declaration for update rule interface
DATA:
    MONITOR       type standard table of rsmonitor WITH HEADER LINE,
    MONITOR_RECNO type standard table of rsmonitors WITH HEADER LINE,
    RECORD_NO     LIKE SY-TABIX,
    RECORD_ALL    LIKE SY-TABIX,
    SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS.
global definitions from update rules
INCLUDE rsbctgn_top.
INCLUDE rsbctgn_update_rules.
FORM routine_9998
TABLES DATA_PACKAGE TYPE tyt_SC_1_full
CHANGING
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
init variables
fill the internal table "MONITOR", to make monitor entries
see OSS note 571669
LOOP AT DATA_PACKAGE.
    IF DATA_PACKAGE-stockcat EQ 'V' OR
       DATA_PACKAGE-stocktype EQ 'V'.
      DELETE DATA_PACKAGE.
    ENDIF.
ENDLOOP.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
ENDFORM.                    "routine_9998
FORM routine_0012
USING
    COMM_STRUCTURE type tys_SC_1__RULE_9
CHANGING
    RESULT         TYPE tys_TG_1_full-ISSCNSSTCK
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
init variables
fill the internal table "MONITOR", to make monitor entries
only goods issue is considered
IF ( COMM_STRUCTURE-processkey EQ '100'   "Other Issues
    OR COMM_STRUCTURE-processkey EQ '101'   "Returns / Vendor
    OR COMM_STRUCTURE-processkey EQ '104'   "Material Transfer
    OR COMM_STRUCTURE-processkey EQ '105'   "Stock Adjustment InvD
    OR COMM_STRUCTURE-processkey EQ '106'   "Stock Adjustment Other
    OR COMM_STRUCTURE-processkey EQ '110' ) "Issue from Stock Transfer
   AND COMM_STRUCTURE-bwapplnm EQ 'MM'
only movements which are relevant for stock control
   AND COMM_STRUCTURE-stockrelev EQ '1'
   AND COMM_STRUCTURE-cpquabu <> 0.
only consignment stock is considered
    CASE COMM_STRUCTURE-stockcat.
      WHEN 'K'.
        RESULT = COMM_STRUCTURE-cpquabu.
        RETURNCODE = 0.
      WHEN space.
        IF COMM_STRUCTURE-stocktype CA 'KLM'.
          RESULT = COMM_STRUCTURE-cpquabu.
          RETURNCODE = 0.
        ELSE.
          RETURNCODE = 4.
        ENDIF.
      WHEN OTHERS.
        RETURNCODE = 4.
    ENDCASE.
ELSE.
if the returncode is not equal zero, the result will not be updated
    RETURNCODE = 4.
ENDIF.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
ENDFORM.                    "routine_0012
FORM routine_0014
USING
    COMM_STRUCTURE type tys_SC_1__RULE_10
CHANGING
    RESULT         TYPE tys_TG_1_full-RECCNSSTCK
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
init variables
fill the internal table "MONITOR", to make monitor entries
only goods receipt is considered
IF ( COMM_STRUCTURE-processkey EQ '000'   "Other Receipts
    OR COMM_STRUCTURE-processkey EQ '001'   "Goods Receipt / Vendor
    OR COMM_STRUCTURE-processkey EQ '004'   "Material Transfer
    OR COMM_STRUCTURE-processkey EQ '005'   "Stock Adjustment InvD
    OR COMM_STRUCTURE-processkey EQ '006'   "Stock Adjustment Other
    OR COMM_STRUCTURE-processkey EQ '010' ) "Receipt from Stock Transfer
   AND COMM_STRUCTURE-bwapplnm EQ 'MM'
only movements which are relevant for stock control
   AND COMM_STRUCTURE-stockrelev EQ '1'
   AND COMM_STRUCTURE-cpquabu <> 0.
only consignment stock is considered
    CASE COMM_STRUCTURE-stockcat.
      WHEN 'K'.
        RESULT = COMM_STRUCTURE-cpquabu.
        RETURNCODE = 0.
      WHEN space.
        IF COMM_STRUCTURE-stocktype CA 'KLM'.
          RESULT = COMM_STRUCTURE-cpquabu.
          RETURNCODE = 0.
        ELSE.
          RETURNCODE = 4.
        ENDIF.
      WHEN OTHERS.
        RETURNCODE = 4.
    ENDCASE.
ELSE.
if the returncode is not equal zero, the result will not be updated
    RETURNCODE = 4.
ENDIF.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
ENDFORM.                    "routine_0014
FORM routine_0041
USING
    COMM_STRUCTURE type tys_SC_1__RULE_11
CHANGING
    RESULT         TYPE tys_TG_1_full-GN_VENDOR
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
init variables
fill the internal table "MONITOR", to make monitor entries
... determine consolidated key
IF COMM_STRUCTURE-stockcat EQ 'K'.
    PERFORM gn_get_global_key TABLES MONITOR
                          USING    COMM_STRUCTURE-gn_r3_ssy
                                   g_c_bwbeoty_r3vendor
                                   COMM_STRUCTURE-vendor
                                   RECORD_NO
                                   RECORD_ALL
                          CHANGING RESULT
                                   ABORT.
if the returncode is not equal zero, the result will not be updated
Endif.
RETURNCODE = 0.
ENDFORM.                    "routine_0041
FORM routine_0010
USING
    COMM_STRUCTURE type tys_SC_1__RULE_12
CHANGING
    RESULT         TYPE tys_TG_1_full-ISSVS_VAL
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
init variables
fill the internal table "MONITOR", to make monitor entries
only goods issue is considered
IF ( COMM_STRUCTURE-processkey EQ '100'   "Other Issues
    OR COMM_STRUCTURE-processkey EQ '101'   "Returns / Vendor
    OR COMM_STRUCTURE-processkey EQ '104'   "Material Transfer
    OR COMM_STRUCTURE-processkey EQ '105'   "Stock Adjustment InvD
    OR COMM_STRUCTURE-processkey EQ '106

Transporting - VOFM Routine to Quality Server

Dear Experts,
I have created a routine in VOFM transaction named 911 (Formula-Condition Base Value)
For the assignment of Tax Procedure in 200 Client.
For the testing and the assignment purpose we used SCC1 Transaction to transfer the assignment from 200 to 220.
Now we need to transport it to 400 Client (Quality).
I have transported the request from 200 to 400.
Also i have check in the client 400, program is there.
But it is not affecting the functionality whichever we get in 200 & 220 client.
Also if i go to transaction VOFM-Formula-Condition Base Value that routine is not there in 400 client.
Kindly help me the steps which Technical / Functional has to do.
Regards,
Ragunathan.R

Hi,
I have executed the report RV80HGEN in client 400.
But not getting the routine in VOFM-Formula-Condiion Base Value.
Also i have checked the note(22808) in that they gave that the tables TFRM & TFRMT contains the entries of the routine
For Example : TFRM-GRPZE - PFRA
                       TRRM-GPRNO - 911 etc..
AND TFRMT-SPRAS = E
        TFRMT-GRPZE = PFRA
        TFRMT-GRPNO = 911 etc.
I have the above entried in 200 client in respective tables but in 400 client i dont have the entries.
What do i need to do to get those entries theres?
Also in 400 client RV63A911 include is not there after transporting that routine from 200 to 400.
That is generated by system automatically.
What to i need to do to get that include in the client 400 also?
Kindly help me to resolve the issue.
Regards,
Ragunathan.R

VOFM routines activation

Similar Messages

Maybe you are looking for