Error RF -BELEG
Hi
Whem i am creating stocks in t.code MIGO with movement type 501,the document is OK but unable to post it.The following error is displayed
ERROR:For object RF-BELEG AUSL ,number range interval 49 does not exist FBN1.
Note:AUSL is my company code.
I have also created number range interval.
Thanks
Regards
Hema
hi hema,
go to transaction code FBN1 and enter your company code
then click on insert interval tab
then click on insert interval tab and then enter N0=49
and maintain the number range
this will reslove your problem
REward points if the answer is helpful
Regards,
Murali
Similar Messages
-
Unable to release to accounting on VF02 - Inconsistency on posting tables
Hi Everyone,
We are unable to release a billing document on VF02. IF we check on SM13, it generates an error on FM RV_INVOICE_POST.
Error details is "V2 030: Inconsistency in the posting tables for document XXXXXXXX"
We have checked the ABAP editor but we are unable to interpret the code:
On subroutine PERFORM VBPA_BEARBEITEN from RV_INVOICE_POST, program passes value of xvbfa-vbeln to structure beleg, because of that beleg-id changes from '$' to 0 because xvbfa-vbeln already has a value.
LOOP AT xvbfa WHERE updkz EQ updkz_new.
beleg = xvbfa-vbeln.
PERFORM vbrk_belegnummer_ermitteln.
xvbfa-vbeln = xvbrk-vbeln.
MODIFY xvbfa.
ENDLOOP.
But on subroutine vbrk_belegnummer_ermitteln there is a condition on beleg-id which is cause of the error:
IF beleg-id NE '$'.
MESSAGE a030 WITH beleg.
ENDIF.
Please advise. Thanks.sorry i have to correct my post, the code should be:
LOOP AT xvbpa WHERE updkz = updkz_new.
beleg = xvbpa-vbeln.
PERFORM vbrk_belegnummer_ermitteln.
xvbpa-vbeln = xvbrk-vbeln.
MODIFY xvbpa.
ENDLOOP.
NOT vbfa.
I will look on OSS note that you said, see if it works. -
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,
PrabhakarHi 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 -
Error Message no. FICUSTOM098
Dear Experts
I am getting the below error while posting the downpayment in FB01 T.code, my client doesn't want to use the F-48 to make the down payment. so i used the FB01 down payment since parking & posting option is available for FB01.
No Funds Management invoice reference in the document splitting data
Message no. FICUSTOM098
Diagnosis
You have activated the online payment update in Funds Management and are posting a document for which the FM invoice reference is not set in document splitting.
Procedure
This message normally only occurs for errors in system configuration. These include:
Using incorrect financial transactions (for example, financial transaction 50 for open item-managed accounts)
Incorrect customizing for document splitting
This message should only be ignored in extreme emergencies. Even if the document can still be posted, the error that occurred will cause problems later on, such as:
Missing updates of follow-on documents
Termination when posting payment documents
Regards
AnilHi Anil,
Please check if the SAP correction Notes below are valid to your current release/package:
1571597 FICUSTOM088 for FI clearing lines
1621286 FICUSTOM098 for postings with financial transactions 30-50
1634237 FICUSTOM098 erscheint beim Buchen vorerfasster Belege nicht
1566669 Error FICUSTOM098 in FI transfer postings(30-90)
1553089 Message FICUSTOM98 displayed in error
1561611 Message FICUSTOM98 displayed in error
1568902 FICUSTOM098 during goods receipt
It can resolve your issue.
Best Regards,
Vanessa. -
'SAPSQL_ARRAY_INSERT_DUPREC' error while cancellation of credit memo.
Hi,
I'am cancelling a credit memo created through 'Sales Return'.When I save the document it gives the message that billing document is created, but just after sometime it shows 'Error info... 00 671: ABAP/4 processor: SAPSQL_ARRAY_INSERT_DUPREC. I've checked SAP notes:208627,154638 and 6080 regarding the mentioned error.
System behaves normally when I cancel an ordinary billing document(cancellation type S1) but when I cancel credit memo (Billing Cancellation type S2) it shows error.Part of the short dump is:
The termination occurred in the ABAP program "SAPLV60U" in "KONV_BEARBEITEN".
The main program was "RSM13000 ".
The termination occurred in line 28 of the source code of the (Include)
program "LV60UF0K"
of the source code of program "LV60UF0K" (when calling the editor 280).
The program "SAPLV60U" was started in the update system.
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "KONV_BEARBEITEN" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLV60U ". Its source code starts in line 11
of the (Include) program "LV60UF0K ".
Source code extract
000010 ***********************************************************************
000020 * Unterroutinen RV-Fakturierung *
000030 * *
000040 * KONV_BEARBEITEN *
000050 ***********************************************************************
000060
000070
000080 * *
000090 * FORM KONV_BEARBEITEN *
000100 * *
000110 FORM KONV_BEARBEITEN.
000120
000130 CHECK: OHNE_KONV = SPACE.
000140 XVBRK_TABIX = 0.
000150 LOOP AT XVBRK WHERE UPDKZ NE UPDKZ_NEW.
000160 DELETE FROM KONV WHERE KNUMV = XVBRK-KNUMV.
000170 ENDLOOP.
000180
000190 LOOP AT XKOMV.
000200 KONV = XKOMV.
000210 BELEG = XKOMV-KNUMV.
000220 IF BELEG-ID = '$'.
000230 PERFORM VBRK_BELEGNUMMER_ERMITTELN.
000240 XKOMV-KNUMV = XVBRK-KNUMV.
000250 ENDIF.
000260 MODIFY XKOMV.
000270 ENDLOOP.
> INSERT KONV FROM TABLE XKOMV.
000290 IF SY-SUBRC NE 0.
000300 MESSAGE A100 WITH 'KONV' SY-SUBRC XKOMV-knumv.
000310 ENDIF.
000320
000330 ENDFORM.
000340 *eject
Please help.
Thanks with Regards.
ManojHI,
We have the same problem , can you please give me an update relating the way you solve it ?
Thanks in advance
Regards -
Error while reading trip trip number from screen memory
I am experiencing the following:
1.When I create a Travel Request with Travel Advance and save the report, I receive no error.
2.I update the request with an estimated cost and save the request, I receive no error.
3.I update the request with u2018Request accommodation/transportation (Outbound flight, Return Flight, Hotel and Car rental) and save the report , I receive an error u2018Error while reading trip <trip number> from screen memoryu2019
4.I remove the estimated cost and save the request, I get an information u2018Personnel number 00075271 could not be locked after the Commit Worku2019
5.When I look at the Cluster table (BELEG) using PRTE, I discover that it stored the Flight expense type with the estimated cost entered in Step 2, even when I delete all the flight from the request.
Note: All the expense types are configured as 'Estimated cost, No Reimbursement to Employee'
Please helpAll,
We applied OSS note 1135084 and it resolved the issue. -
Va01:errors during posting sales order
Hi there,
can anyone help me on the error log during posting sales order via va01? the checking of sales order is correct.
Runtime Errors MESSAGE_TYPE_X
Date and Time 2009.02.17 10:11:37
Short dump has not been completely stored (too big)
|Short text |
| The current application triggered a termination with a short dump. |
|What happened? |
| The current application program detected a situation which really |
| should not occur. Therefore, a termination with a short dump was |
| triggered on purpose by the key word MESSAGE (type X). |
|What can you do? |
| Note down which actions and inputs caused the error. |
| |
| |
| To process the problem further, contact you SAP system |
| administrator. |
| |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
|Error analysis |
| Short text of error message: |
| Maintain the current CRM release (table CRMPAROLTP) |
| |
| Long text of error message: |
| Diagnosis |
| Various transfer errors occur when transferring SAP sales orders to |
| CRM or there is no status update or the status update has errors |
| when transferring from CRM to the SAP system. This is caused by an |
| incorrect entry for the CRM release in the SAP table CRMPAROLTP, or |
| no entry is maintained at all. |
| System Response|
| To avoid data inconsistencies, this message causes a short dump. |
| Procedure |
| Maintain table CRMPAROLTP in your SAP system as is described in SAP |
| Note 691710 and then repeat the process again. |
| Procedure for System Administration |
| |
| Technical information about the message: |
| Message class....... "V3" |
| Number.............. 302 |
| Variable 1.......... " " |
| Variable 2.......... " " |
| Variable 3.......... " " |
| Variable 4.......... " " |
|How to correct the error |
| Probably the only way to eliminate the error is to correct the program. |
| - |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "MESSAGE_TYPE_X" " " |
| "SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN" |
| "BAPIDATEN_ERMITTELN" |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information:|
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
|User and Transaction|
| Client.............. 200 |
| User................ "SAMSON"|
| Language key........ "E" |
| Transaction......... "VA01 " |
| Program............. "SAPMV45A" |
| Screen.............. "SAPMV45A 4001" |
| Screen line......... 65 |
|Information on where terminated |
| Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN". |
| The main program was "SAPMV45A ". |
| |
| In the source code you have the termination point in line 338 |
| of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN". |
|Source Code Extract |
|Line |SourceCde |
| 308| else. |
| 309|*-----Nicht unterstu9EF7zt, Abbruch |
| 310| message a301(v3). |
| 311| endif. |
| 312| endif. |
| 313| |
| 314|*-Szenario A pru9EE4en |
| 315| if lv_scenario_a = 'A'.|
| 316| vbak-vbkla+2(1) = lv_scenario_a. |
| 317| endif. |
| 318| |
| 319|*-ermitteln CRM-Release |
| 320| call function func_name |
| 321| exporting |
| 322| i_paraname = 'CRM_RELEASE' |
| 323| importing |
| 324| e_parval1 = lv_parval1. |
| 325| lv_release_crm = lv_parval1+0(3). |
| 326| |
| 327|* If lv_release_crm empty => X-message (correct download not possible) |
| 328| if da_download_active = charx. |
| 329| CALL FUNCTION 'CRM_CONNECTED' |
| 330| IMPORTING|
| 331| CRM_CONNECTED = lv_crm_connected |
| 332| EXCEPTIONS |
| 333| NO_CRMRFCPAR = 1 |
| 334| OTHERS = 2 |
| 335| . |
| 336| IF sy-subrc = 0 and lv_release_crm = space and |
| 337| lv_crm_connected = charx. |
|>>>>>| message x302(v3). |
| 339| ENDIF. |
| 340| endif. |
| 341| |
| 342|*-Fu9EEElen der View fu9EF5 das Ermitteln der Auftragstabellen |
| 343| da_sales_view-partner = charx. |
| 344| da_sales_view-sdcond = charx. |
| 345| da_sales_view-sdcond_add = charx. |
| 346| da_sales_view-contract = charx. |
| 347| da_sales_view-text = charx. |
| 348|*-bei mehr als 1000 Belegflusssu92DEzen werden Daten nicht ermittelt |
| 349| if lv_tabix_vbfa < 1000. |
| 350| da_sales_view-flow = charx. |
| 351| endif. |
| 352| da_sales_view-billplan = charx. |
| 353| da_sales_view-configure = charx. |
| 354| da_sales_view-credcard = charx. |
| 355| |
| 356|*-Im Standardszenario soll eine manuelle u818Ederung eines CRM Belegs|
| 357|* (ab CRM Release 30A) nicht zuru9EDEk ins CRM gesendet werden. Das |
any responses will be awarded,
regards,
samsonHi,
Maintain the current CRM release.
The dump might have occurred when transferring SAP sales order to CRM.
This has caused a error in SAP table CRMPAROLTP .
Go to SE91 provide the message class & message number, then click where-used-list & select the program check box.It will show you the program name MV45AF0B_BAPIDATEN_ERMITTELN.
Just check the program with the ABAPer.
Hope this helps.
Regds.......
Sumit -
Error at the time of saving sales order
Hi Sapfans,
at the time of saving the order i am getting the following error
please help me how to solve it
please help me fast
thanks and regards
srinivas
Runtime Errors MESSAGE_TYPE_X
Date and Time 19.11.2007 15:19:18
Short dump has not been completely stored (too big)
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Maintain the current CRM release (table CRMPAROLTP)
Long text of error message:
Diagnosis
Various transfer errors occur when transferring SAP sales orders to
CRM or there is no status update or the status update has errors
when transferring from CRM to the SAP system. This is caused by an
incorrect entry for the CRM release in the SAP table CRMPAROLTP, or
no entry is maintained at all.
System Response
To avoid data inconsistencies, this message causes a short dump.
Procedure
Maintain table CRMPAROLTP in your SAP system as is described in SAP
Note 691710 and then repeat the process again.
Procedure for System Administration
Technical information about the message:
Message class....... "V3"
Number.............. 302
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Trigger Location of Runtime Error
Program SAPMV45A
Include MV45AF0B_BAPIDATEN_ERMITTELN
Row 338
Module type (FORM)
Module Name BAPIDATEN_ERMITTELN
Source Code Extract
Line SourceCde
308 else.
309 *-----Nicht unterstützt, Abbruch
310 message a301(v3).
311 endif.
312 endif.
313
314 *-Szenario A prüfen
315 if lv_scenario_a = 'A'.
316 vbak-vbkla+2(1) = lv_scenario_a.
317 endif.
318
319 *-ermitteln CRM-Release
320 call function func_name
321 exporting
322 i_paraname = 'CRM_RELEASE'
323 importing
324 e_parval1 = lv_parval1.
325 lv_release_crm = lv_parval1+0(3).
326
327 * If lv_release_crm empty => X-message (correct download not possible)
328 if da_download_active = charx.
329 CALL FUNCTION 'CRM_CONNECTED'
330 IMPORTING
331 CRM_CONNECTED = lv_crm_connected
332 EXCEPTIONS
333 NO_CRMRFCPAR = 1
334 OTHERS = 2
335 .
336 IF sy-subrc = 0 and lv_release_crm = space and
337 lv_crm_connected = charx.
>>>>> message x302(v3).
339 ENDIF.
340 endif.
341
342 *-Füllen der View für das Ermitteln der Auftragstabellen
343 da_sales_view-partner = charx.
344 da_sales_view-sdcond = charx.
345 da_sales_view-sdcond_add = charx.
346 da_sales_view-contract = charx.
347 da_sales_view-text = charx.
348 *-bei mehr als 1000 Belegflusssätzen werden Daten nicht ermittelt
349 if lv_tabix_vbfa < 1000.
350 da_sales_view-flow = charx.
351 endif.
352 da_sales_view-billplan = charx.
353 da_sales_view-configure = charx.
354 da_sales_view-credcard = charx.
355
356 *-Im Standardszenario soll eine manuelle Änderung eines CRM Belegs
357 * (ab CRM Release 30A) nicht zurück ins CRM gesendet werden. DasHI,
This error is because of crm release patch.
You can update this patch.
Use Transaction code se16.
Type the table name-CRMPAROLTP
Go in New Entries
Type 'CRM_RELEASE' In First Field(PARNAME)
Type '40A' In Value 1 i.e. 5th Field
Save.
This will solve your problem.
If this is useful please give reward points.
Regards,
Ashok -
IDOC - Message FIDCCP1 - Error reading company code
Hi all,
I am trying to create a FI document using an IDOC type FIDCCP01. Everything seems to be OK, but always my IDOC gets status 51 and message:
Error reading company code
Message no. F1309
I am sure that I am using the correct company code, I actually created a document manually and I am using the same data from it into my IDOC. I put the correct company code in every field where company code is required, still not working.
Any suggestion will be highly appreciated.
ThanksHi,
I believe you are filling the company code in the field E1FIKPF-BUKRS, if you are filling the company code in that field that field is 6 characters length and the actual company code is 4 characters in length.
Are you using the function module IDOC_INPUT_FIDCC1 for posting the idoc.
Put a break point in the below location
IF X-SEND_C1 = '2'. "vorerfaßten Beleg buchen
PERFORM IDOC_VERARBEITEN_VORERF_BELEG USING K_MESTYP_C1.
and then debug, you will understand the problem.
Error is being thrown in the below perform.
PERFORM LESEN_T001_KTOPL USING E1FIKPF-BUKRS. "KTOPL_NACH lesen
FORM LESEN_T001_KTOPL USING LTK_BUKRS.
SELECT SINGLE * FROM T001
WHERE BUKRS = LTK_BUKRS.
CHECK NOT SY-SUBRC IS INITIAL.
PERFORM IDOC_STATUS_FUELLEN USING 'E'
'F1'
'309'
LTK_BUKRS
ENDFORM. "LESEN_T001_KTOPL
Check the above things in debug mode and then you will understand the problem correclty and let me know, so that i can help you.
Thansk,
Mahesh. -
Runtime error : table_invalid_idex When VF03 for cancel billing doc. flow
Dear Gurus,
i'm facing a problem, when i want to display document flow for my cancel billing was getting error.
Dump analysis :
602 PERFORM vbfa_tab_append.
603 EXIT.
604 ELSE.
605 CLEAR vbfa_index_key-posnn.
606 READ TABLE vbfa_index WITH KEY vbfa_index_key
607 BINARY SEARCH.
608 ENDIF.
609 ENDIF.
610 ENDIF.
611 IF sy-subrc = 0.
612 tabix = vbfa_index-tabix + zaehler - 1.
613 vbfa_tab = vbfa.
614 IF vbfa-vbeln = gv_storno_vbeln.
615 vbfa_insert = vbfa_index-tabix + zaehler.
616 ADD 1 TO zaehler.
617 READ TABLE vbfa_tab INDEX vbfa_insert.
618 vbfa_tab = vbfa.
619 INSERT vbfa_tab INDEX vbfa_insert.
620 ADD 1 TO vbfa_insert.
621 SELECT * FROM vbfa WHERE vbelv = vbfa_tab-vbeln
622 AND vbtyp_v = vbfa_tab-vbtyp_n.
623 vbfa_tab = vbfa.
624 ADD 2 TO vbfa_tab-stufe.
625 INSERT vbfa_tab INDEX vbfa_insert.
626 ADD 1 TO zaehler.
627 ENDSELECT.
628 vbfa_insert = tabix.
629 ELSE.
630 IF vbfa-vbeln NE gv_storno_vbeln.
631 vbfa_insert = vbfa_index-tabix + zaehler.
---> INSERT vbfa_tab INDEX vbfa_insert
633 ADD 1 TO zaehler.
634 ENDIF.
635 ENDIF.
636 ELSE.
637 PERFORM vbfa_tab_append.
638 EXIT.
639 ENDIF.
640 ELSE.
641 PERFORM vbfa_tab_append.
642 EXIT.
643 ENDIF.
644 ENDIF.
645 DESCRIBE TABLE xvbfa.
646 IF sy-tfill = 1 OR
647 *archivierter Beleg
648 ( sy-tfill = 0 AND NOT vbfa_tab-vbelv IS INITIAL ).
649 ADD 1 TO vbfa_insert.
650 ENDIF.
651 ENDIF.
i'v found sap note 978073 but did not solved my problem. Please reply if anyone know the answer (solution) for this problem.
Many-many thanks for your answer
Regards,
ARA
Edited by: Agung Rahmat on Jan 19, 2010 5:36 AM
Edited by: Agung Rahmat on Jan 19, 2010 5:37 AM
Edited by: Agung Rahmat on Jan 19, 2010 5:38 AMDear All,
this is part of error analysis :
When changing or deleting one or more lines of the internal table
\PROGRAM=SAPMV75F\DATA=VBFA_TAB[] or when inserting in the table
"\PROGRAM=SAPMV75F\DATA=VBFA_TAB[]", 0 was used as
the line index. An index less than or equal to zero is not
allowed.
The error can occur when using the following options:
1. "INDEX idx" for specifying the line number in the table
"\PROGRAM=SAPMV75F\DATA=VBFA_TAB[]"
where you want to change, insert or delete.
2. "FROM idx" for specifying the start index when deleting a line
area from or inserting a line area into the table
"\PROGRAM=SAPMV75F\DATA=VBFA_TAB[]".
3. "TO idx" for specifying the end index when deleting a line
area from or inserting a line area into the table
"\PROGRAM=SAPMV75F\DATA=VBFA_TAB[]".
At the time of the termination, the table contained 11 lines.
hope that can help.
Thanks & regards,
ARA -
Runtime Error when trying to trigger smartform from VL03N
Hi all,
i am having a runtime error while trying to triger my smartforms from transaction VL03N.
The error is 'The current ABAP program "SAPLV60U" had to be terminated because it has come across a statement that unfortunately cannot be executed.'
The it's in the include: "LV60UF0K"
| 21| LOOP AT XKOMV.
| 22| KONV = XKOMV.
| 23| BELEG = XKOMV-KNUMV.
| 24| IF BELEG-ID = '$'.
| 25| PERFORM VBRK_BELEGNUMMER_ERMITTELN.
| 26| XKOMV-KNUMV = XVBRK-KNUMV.
| 27| ENDIF.
| 28| MODIFY XKOMV.
| 29| ENDLOOP.
|>>>>>| INSERT KONV FROM TABLE XKOMV.
| 31| IF SY-SUBRC NE 0.
| 32| MESSAGE A100 WITH 'KONV' SY-SUBRC XKOMV-knumv.
| 33| ENDIF.
can anyone help me on this please..
Thanks in advance
Regards
NitinThis looks like standard SAP code, your best bet is to log this as a problem on service.sap.com
Regards,
Nick -
Hi all experts,
I tried to change a document belongs to 2004 year in this year through FBV2. Now we are using ECC 6.0.
when i change and save the message changes have made is coming. after that immediately the mail was coming to my inbox (SO01) stating Update was terminated - Error Info... CD 328: DUPREC:POS&BELEG&200S01304210000142004
kindly help me in this regard.
Regards,
SomaHi Mark,
We have this same issue in transaction F-65
I believe that when a new screen template is configured, a new screen is generated within function group F040. A later action (applying a hotpack??) has removed this screen, but the config (in table T021D) still points the processing to the screen even though it has been removed.
Did you find a solution? We want to get the screen back as it is still valid to use this screen template in the business
Thanks
Ben -
Error in starting Adobe Bridge in Photoshop CS2
I've just installed Photoshop CS2, however upon opening Adobe Bridge this error message appears " The application has failed to start because libagluc28.dll was not found. Reinstalling to application may fix the problem"
I have reinstalled and click repair but to no avail
I followed Adobe Support Knowledgebase solution and run CMD and this appears:
c:Documents and Settings/Jesus M Ferraris>
then i entered the command
cacls c:\windows\installer /T /E /C /G administrators:F
but an error message appears - 'cacls' is not recognized as an internal or external command, operable program or bathc file
I also entered the next command
cacls "c:\documents and setting\all users" /Y /E /C /G administrators:F
still the same error as above appears, Please help, have I miss something or was my procedure correct...
P4, 512ram, WXP 80gHDVery useful.
Good Luck.
My
Si
tes -
Windows Vista: Ipod Error Message, no longer read by PCs
Hello,
I have a 5th generation black ipod video with 30GB of memory.
The other day I hooked it up to my laptop (Toshiba, 4 months old) that it's been functioning on with no problems whatsoever. This weird error message flashed twice about it not being able to sync because of some software problem.
Eversince then, the only thing I can charge my ipod on is the family treadmill in the basement (~_~) as no other computer in the house recognizes it. I can't even charge it through the wall sockets, either.
I have changed the ipod cord, still no luck. I've also reset the device about 3 or 4 times and uninstalled, restarted the laptop then reinstalled itunes. I would like to reset it back to factory settings but that's impossible as computers/laptops don't pick it up. I live very far from a Mac store...
What's a girl to do? I can't live without my Busta Rhymes and Wu-Tang Clan!
Any advice would be greatly appreciated! Thanks!you have to update Vista go to this site and up-date http://windowsupdate.microsoft.com
-
Error while offsetting a variable
Hello Experts
I want to display the data for last 5 years in my query. So I tried using the SAP exit variable Current Calendar Year (0CYEAR) and the offset it by 5. However, I am getting the following error message for the query "System error in program SAPLRR12 and form REP_ASSIGN_INITIAL_OPT-01"
Any Help on this is appreciated and points will be assigned.
ThanksThanks Chetan for your prompt reply. I have assigned points.
But I would appreciate if you help me clear my understanding of offseting a variable.
Say if the Current Calendar Year variable returns 2008, then will offseting that variable by 5 return me the data for years 2008, 2007, 2006, 2005 , 2004. Or, will it just return me the data for 2008 - 5 = 2004 only.
Thanks
Rishi
Maybe you are looking for
-
I am having a hard time trying to set up my cc info on iTunes. I keep getting a message that says invalid security code which is on the back of my card and the same card I use to make purchases online with all the time. What may be the problem?
-
Hello, I'm new to using BB so first apologies for such a silly question perhaps. Just got it delivered, and I'm intrigued by the sticker on the side that says "when operated in France, this equipment uses non harmonized frequency bands". I'm French
-
Material Description getting truncated in LI04 print
Hi All, When we print Physical Inventory document in LI04 and using standard report RLLI0400 the system takes on 20 char in material description and truncates rest of the description. However SAP given Note 538759 - Modif.note to extend material Des
-
Firefox keeps opening in a new tab
I continuously have to disable the option within Firefox to open new windows in a new tab instead. This seems to work properly for an intermittent amount of time and then randomly, I'll click a link and instead of being redirected to a new window, th
-
Reg. Display of Output exceeds 255 characters as spool list
Dear Experts, My requirement is that i need to display output that exceeds 255 characters in length as spool list. How should i achieve it? Regards, Ramesh Manoharan