Bi Content Transformation's

Hi Friends,
I've taken Bi content objects
DataSource: 0FI_AR_4
ODS: 0FIAR_O03
CUBE: 0FIAR_C03
I've just installed and replicated and then started instaling respective BI Content cube (ofiar_c03) by setting grouping IN DATA FLOW BEFORE, but here the problem is that transformation's aren't getting formed automatically as in the case earlier versions it used to be done automatically, but in BI 7.0 it seems to be done manually. Why is it so?
Can anybody give me the exact solution? is there anyway of getting done transformations automatically? it's very difficult to do tranformations since there are a lot of fields and infoobjects.
Waiting for your inputs'
Regards,
BalajiReddy

Balaji
Take a look at the below link.
Re: Transformation Rules
If it really helps, dont forget to assign points.
Thanks
Prasad

Similar Messages

BI Content Transformation Rule for Data Source 2LIS_03_BX

Hi All,
I am using BI content info cube 0RT_C54 for queries. I am uanble to find BI content transformation rules for the Data Source 2LIS_03_BX. In "Network Display of the data flow" I am able to see the transformation rules for this data source. How can I activate and use the same ?
Regards,
Rohit

Hi ankit,
Have u done all the mandatory settings before running setup for stock init.
1. Determine industry sector.
2. Maintainng process keys,
3. Maintining Application Indicatore in BF11.
Also activate other two ds - 2lis_03_bf & UM.
Then try to fill again setup data.
Hope this helps to u.
Thanks
Dipika

2lis_03_BF transformation

Hi,
i am using standard Business content transformation for BF ,
when i trying to activate the transformation it is showing syntax error in start routine.
error: E:In PERFORM or CALL FUNCTION "ROUTINE_9998", the actual parameter "SOURCE_PACKAGE" is incompatible with the formal parameter "DATA_PACKAGE".
The routine is
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 Stock type.
 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: 0COORDER Order number.
 COORDER TYPE /BI0/OICOORDER,
 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: 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: 0RMA_XCC RMA Cross-Company Code Stock Transfer.
 RMA_XCC TYPE /BI0/OIRMA_XCC,
 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 ( C

Hello,
you have to convert the incomming data in SOURCE_PACKAGE to a local table, which has the structure of the called routine "routine_9998", because the parameter DATA_PACKAGE have to reference to the same type.
Please insert your conversion before statement in startroutine method:
Your conversion
TABLES
SOURCE_PACKAGE --> replace this line by your own internal table with type of DATA_PACKAGE
CHANGING
l_abort.
Regards,
André
Edited by: André Klos on Jun 24, 2008 9:33 AM

File Sender Adapter transformation problem

Hi everyone,
I have a problem tha might be quite simple to solve but I'm completely lost And some help would be apreciated
We have an "File -> RFC -> File" scenario implemented using BPM, in our case the file is already in an XML format and we dont have control on the creation on that file, some old application generates it. The problems is that no matter if we build the data type or if we use an external definition, PI always adds the namespace to the message using the tag xmlns:ns0="namespace...." and in our case the when we test the interface is expecting something like this:
If we tests with the original file PI triggers an Mapping Error, in fact, if whe load the file in the mapping test section at design time we can reproduce the error. When we change the file format mannualy and we just add the "ns0" and the attribute xmlns:ns0="Some namespace....." it works just fine. The problem is that we cannot change the program that generates the files and I don´t have any clue on how to solve this on PI side. We don't know which should be the approach.. content transformations in the CC, XSLT, or create an VBS at operating system level to change all the files before PI runs, etc...
Any ideas would be very helpful.
Gustavo Balboa

Hi Gouri,
I was sure that would be a very simple solution jejejeje..... thank you very much. You were right. I just remove the namespace of the data type, and now is working just fine.
I always use the namespace and I thougth that was mandatory always because in the repository the field is marked as mandatory...
Again, thank you!
Best Regards
Gustavo Balboa

BI 7.0 BI_Content Transformations.

Experts:
We are on this BI_Cont patch level:
BI_CONT 703 0014 SAPKIBIIQ4 Business Intelligence Content Component Supp. Pkg.
We are installing BI content for many cubes. I'm not finding many Transformations in this content level.
I would like to minimize the migration effort and the manual correction of transformation routines that do not convert correctly.
Can you suggest how I can locate more BI Content Transformations or recommend how best to correct transformation routine conversion errors?
Thanks
Den

BI content with transformations is a widely discussed topic and no one is quite sure of when the content is to be migrated . In all likelihood - some of it has but all of it has not. The best bet would be to check the release notes for the same in help.sap.com but then trawling the same is tedious....
We had similar issue of installing BCont as the manna for migrating all the business content but decided otherwise since most of the content was not yet in 7.0 versions...

Related Content Service in HCM

Hi,
I configured a related content service for a custom page but unfortunately the related information does not appear for the page. Does anyone have any idea what am i missing?
We are running on PeopleSoft HCM 9.1/PeopleTools 8.50.
Anand

Hi,
Cisco's Content Transformation Engine was one of the first appliance-based solution on the market to deliver web-based applications to a variety of devices including Cisco IP Phones, Wireless Application Protocol (WAP) phones, personal digital assistants (PDAs).
Content transformation technology helps customers transparently optimize Web content for users accessing information with a variety of mobile or wired devices such as WAP PDAs, cell phones, Research in Motion (RIM) devices, or even Cisco IP phones.
The Content Services Gateway (CSG) provides the capability to examine the mobile wireless and wireline IP datastream beyond the IP and TCP/UDP headers so as to enable billing based on the content being provided to the end user and hence supports billing for the new wireless data services.
For details refer:
http://www.cisco.com/en/US/products/sw/wirelssw/ps779/products_white_paper09186a0080088853.shtml
http://www.cisco.com/pcgi-bin/Support/browse/psp_view.pl?p=Hardware:CTE1400

Meetup in Orange County/CA About Migrating content into CQ

Just wanted to let everybody know that we have a presentation on how to automatically transfer a site into CQ on Wed March-20
The meetup can be found at http://www.meetup.com/OC-CQ-Sling-JCR-User-Group/events/106181442/
Would be great to see as many of you there as possible.
CQ 5 - Content Migration Approaches
This presentation describes best practices, techniques and approaches for executing successful content migrations to CQ 5. Learn from three real-world case studies covering large scale content transformations, content restructuring and how to migrate legacy content into CQ 5.
The speaker will be Gaston Gonzalez

Just a friendly reminder, this is a forum where users help other users. It looks like your issue may require a Verizon representative to review your account details. Please contact our customer service team via live chat or email at:
http://www.verizon.com/contactus
If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer that solved your issue as the accepted solution.

How to Print of entire content by endusers ?

We are new on portals and searching for a possibility to print the entire Content of an i-view or page in an easy way by end users. Is this possible ? Via special services / PDF ?
(don't know if this is a developer issue or an installation issue (that's why posted in both forums))

It can be done in a myriad of different ways.
Examples:
1: Create a print-link, which opens op a new page, rendering the same content in a print-friendly way,
2: Via a link; Get the same content, transform it via XML to FO, and use a FOP (FO Processor) to create a PDF, which the user can print or save. Return it to the user in a response stream (dynamically or cached).
3: Open a window (via a link, surprisingly enough ), which renders the exact same content, with another style sheet (css), formatting the content for printing
4: use 2 different CSS for your portal; one for normal view, and one for printing (media="print" - an attribute you can set on the import of CSS into the content). Then the output from the printer will automatically be formatted for printing (via the print-css), when the user chooses to print through the ordinary print-function in the browser. This would apply for all of the portal, not just the content of an iView or Page (unless you open it separately in a new window).
Regards,
/Henrik

Transformation to supply DSO 0RT_DS54 can not be acticated

Hi,
I am trying to activate the Retail Content DSO 0RT_DS54 with the Data Flow befor. I get the DSO activatet and also InfoSources 0RT_PA_TRAN_CONTROL_TR and 2LIS_13_VDITM are active available, no dataflow between DSO and InfoSources.
A message while collecting business content says...
Object 0G33PCXXMC2QXHGGVG89S1TBTF5ROZ82 (Transformation,TRFN) could not be collected
When I try to activate the Transformation for it self I cant find it in rsa1 --> Business Content --> Transformations !?
If anybody would have an Idea I would apreciate.
I am working on the following BW and content versions...
- SAP_BW 700 0018 SAPKW70018 SAP NetWeaver BI 7.0
- BI_CONT 703 0011 SAPKIBIIQ1 Business Intelligence Content

Hi Try and implement these notes 1311698 , 1171293 , 1179880.
Colin

Documenting existing Transformations Mapping

Hi All,
Can any one tell me How to copy and paste all Existing Transformations along with the transformation mappings..
1. I Could not find in all meta data directory.
2. I cud save only as JPG
Is there any other way to get it done?
Thanks,
Hari

Thats a tough job
I just wonder SAP even provided with a table or any other feature as such because they haven't delivered any Standard Content Transformations in the first place - why would a table exist for the same ...

Error while migrating transfer rules

Hi all,
When migrating 2LIS_02_SCL transfer rules to transforamtions I got a shotdump "ASSERTION_FAILED in 'CL_RSTRAN_TEMPLATE->CREATE_ROUTINE" for this I have implemented Snote : 986199 after this when I am migrating transforamtions are getting created but showing syntax errors (for this transfer rules there are standard routines ) .Can anyone help me to sort out this issue.
Regards
KK

Hello,
unfortunately not all transfer rules can be migrated automatically.The migration of the business content transformation is done on customer project base. This means some of the adjustments needs to be done manually.
Please adjust the rules to the ABAP OO compliance.
This how to paper should help:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fc61e12d-0a01-0010-2883-e2fc63ef729b
and
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e73bfc19-0e01-0010-23bc-ef0ad53f2fab
I hope this helps.
Michael

File to Proxy Scenari0, Error in ECC server Messages stucked in Queue

Hi All
we have created a file to proxy scenario in PI & when we are sending the data to Proxy, proxy is not getting executed in SAP ECC & we are getting the following error in out production ECC server & all the messages are getting s
No load could be found for transformation /1SAI/TXSA9475ABE3925030F71D9
could any one of you please help me in resolving this issue.
Thanks
Rinku Gangwani

Hi,
Are you activate the ICF services in ERP system? This issue must be done for the correct execution of proxy channel.
What type of program mapping are you using for the content transformation?
If you use a ABAP mapping program make sure to activate the program correctly.
Best regards
Ivá

Debit/Credit Balances and Account Hierarchy

Hi
I need to show accounts in the Account Hierarchy according to whether the account has a debit or credit balance. For example, if an account has a debit balance, it must be displayed under debtors and if it has a credit balance, under creditors.
How can I do this type of reporting in BPC, when the same d/c indicator as in the Financial Statement Version in ERP is not available in BPC?
Any response appreciated.
L.

Hi Lambertus,
BPC doesn't have something like the financial statement version built in. Neither does BW, actually, but there are business content transformations and queries that use some complex methods to do the kind of reporting you are talking about.
In BPC I think you are going to need three accounts to accomplish this functionality - one in each branch of the hierarchy (accounts A & B in the example), plus one account that you actually load data into (account C in the example), which will not be displayed in the hierarchy. The two accounts in the hierarchy will either be formula accounts (not ideal) or populated using MDX script logic (better because the values will roll up the hierarchy). Your MDX, either in a formula or a script, would need to look something like this:
[ACCOUNT].[#A] = iif([ACCOUNT].[C] >= 0, [ACCOUNT].[C], 0)
[ACCOUNT].[#B] = iif([ACCOUNT].[C] < 0, [ACCOUNT].[C], 0)
Have I tested this code? No. So buyer beware. But hopefully it sets you on the right track.
Ethan

Programmatically Turn Off Printing (Acrobat 6.0)

Hello.
I'm searching (fruitlessly so far) for an option to turn off printing on a PDF. I've gone down multiple avenues and have come up empty to date.
My company is using Documentum SCS and Content Transformation Services (Documentum) to export/convert files to PDF format in a readable location. Through our normal process, we place an overlay on the document using another product, which indicates the status of the file (approved/effective). Since we cannot use the overlay when exporting in this fashion, we've settled on disabling printing for the PDFs.
The preferred solution would be using CTS to set the security, however I don't have a lot of confidence in that solution just yet.
The second preferred method would be for CTS to run a piece of VBS code post-export, which takes the PDFs and sets them to noprint.
The last resort would be to create a Windows service using .NET that waits for new files in the directory and sets them to noprint.
Any solutions to programmatically setting noprint? Any feedback on the path being taken?
Thanks in advance!

If you're looking for a fully automated solution, Acrobat will not be an option.
The only fully automated option Adobe provides would be Adobe LiveCycle Rights Management ES, which you can read about here:
http://www.adobe.com/products/livecycle/rightsmanagement/
If you are interested in a Documentum-direct solution, you would probably get best results asking on some Documentum forums. Most users here work specifically with the Acrobat SDK ( it being an Adobe forum :) ).

SAP KM vs. Documentum

Does anyone know of any documentation or anywhere else that I could find information that compares document management solutions between SAP KM and Documentum?
Thanks, points will be awarded for anything that is helpful.

Hi Michael,
The Knowledge Management platform is delivered within the SAP Enterprise Portal and provides access to an organization's unstructured information (documents). The information may reside in multiple repositories that can be connected to the portal by repository managers. (Some repository managers are delivered by SAP; other can be programmed based on open APIs.) The functions of the KM platform can be exposed to the documents in all connected repositories, given that the respective repository manager allows it.
The major functional areas of KM are: Content Management, which supports the entire lifecycle of documents, including the authoring, storage, management, and display of documents. It also manages the connection between document repositories and the portal and provides collaborative functions such as feedback, rating, subscription, etc. Search and Classification (TREX), which processes search queries on free-text or attributes, and provides automatic classification in taxonomies and text mining. TREX is also used in other building blocks of SAP NetWeaver such as SAP Business Intelligence.
Documentum,produces an enterprise content management system for global enterprises worldwide.
Documentum is widely known for a long history of enterprise content management firsts. Documentum was the first to offer document, web content and rich media content management in one platform. Documentum was the first to achieve mainframe-scale performance with a billion-object repository benchmark. Documentum was the first to introduce XML into a content management system.
Documentum Content Transformation Services is a new offering that provides users a single and easily managed tool from which to perform all content transformations. Using a wizard-based approach, customers can more easily transform common desktop documents and rich media formats -- such as images, audio and video -- into any compatible content type.
Hope this helps.
Regards,
Pooja.

Bi Content Transformation's

Similar Messages

Maybe you are looking for