AFS Elementary Field Extraction (Category Fields)

Hello Guru's,
I have a problem of extracting category fields. The problem is in the mapping of Characteristics (Category) to the Elementary fields in the R3 AFS BW interface. For an example if you take the category characteristic 'Quality" it has two elementary fields,
Stock(J_3ABWEL_QUAL ) & Requirement(J_3ABWEL_QUAL_R). But the problem in R3 is, there is only ONE Characteristic available for "Quality".  In the AFS BW interface it is not possible to map one Characteristic into two Elementary Fields.
Please let me know how to handle this.
Any thoughts will be greatly appreciated.
Thanks
RJ

Hi AFS Gurus,
Could you please help me out?
Cheers,
DM

Similar Messages

  • Extract Category, Attributes data in Multilingual

    Hi experts,
    I'm using the MDMGX to extract the Categories data using the F/M "MDM_COMM_CATEGORIES_EXTR".
    data is populated (in debug mode) in all languages but, when the XML file created its showing only English language data. did I left any configurations / parameter values ?
    Same with the CategoryAttributes data, using F/M  "MDM_COMM_CAT_ATTRIBUTES_EXTR".
        Let me know how to extract the Category data & Attribute data in multilingual and also explain the use of  SETTYPES in the extraction part.If there is another way to extract data ? Please guide me.
    Regards,
    Rupesh K

    Hi Rupesh,
    For given port code define lang dependant field to be extracted under LANG_FIELDS field
    e.g. for extracting country related data the entry should be like given below
    MDM_PORTCODE = LT_Countries
    Table_name = T005T
    LANG_FIELDS= SPRAS=langkey,LANDX=Name,NATIO=Nationality
    here it will fetch data from T005T table from which spras field will be mapped to langkey, landx will be mapped to Name &  Natio to Nationality.
    Just check data u entered under 'LANG_FIELDS' .
    Refer to standard upload files given by SAP delivered with MDM Business content.

  • Extract category attribute value desgin question

    I created a search application which returns a result set of documents that have a custom category. I need to extract the values of the applied category. Right now I'm doing some looping a getting the requestedAttributes until i have the CUSTOM_ALL. I get the values using the internal names.
    Document -> Categories -> CUSTOM_ALL -> Custom Attributes Values
    Is there a better way to do this?

    Unfortunately no, at least as far as I know. I wrote some procedures that I can use in all places where I need category information (procedures like getCatInfoFromFolder, mapInternalToDisplayNames, ....), it took me a while but it saved me a lot of time in later coding.
    Pedja

  • Tables & Fields for AFS characteristics values

    Hi Gurus,
    Need a help to find otu the Characteristic vlues of AFS-Material FIELD NAMES and their TABLE NAMES.
    If any one konws please let me know that will be great.
    Exactly the i want to find out the FIELD NAMES of the Characteristic Values of a AFS Material. Where these characteristics values are going and sitting in Which FIELDS and in which TABLES.....Ok...
    Advance thanks aand Regards,
    Madhu.G

    Sudha,
    You can find all material document details in table MSEG.
    Regards,
    John.

  • Updating SAP fields through BAPI (which are not BAPI parameters)

    Hello,
       I need to update season and collection fields in sales order (AFS), these fields are not in sales order creation BAPI. Can I still somehow use them in extensionin as parameters?? How do we do it?? BAPI: /AFS/BAPI_SALESORD_CREATEFDATA
    Also there is another BAPI /AFS/VBAK_SALESDOCUMENT_CHANGE which has these fields in ITEM_EX table (which is extension for item table provided by SAP), but this dosent update the sales order as well.
    I would appreciate if anyone has a clue how to do this.
    Thanks,
    Amit.

    /AFS/VBAK_SALESDOCUMENT_CHANGE
    Append structure BAPE_VBAP
    J_3ASEAN
    /AFS/COLLECTION
    /AFS/THEME
    Append structure BAPE_VBAPX
    J_3ASEAN              CHAR1
    /AFS/COLLECTION              CHAR1
    /AFS/THEME              CHAR1
    Table: ITEMS_EX
    OPERATION                      009
    DOC_NUMBER                     200000608
    ITM_NUMBER                     000000
    MATERIAL                       2000010022
    UPDAT_FLAG                     I
    SEASON                         C1
    COLLECTION                     DAM
    THEME                          SEG
    Pass the season Fields through EXTENSIONIN structure to update data into tables.
    STRUCTURE                      BAPE_VBAP
    VALUEPART1                         020000060800000000000000C1 DAM SEG
    STRUCTURE                      BAPE_VBAPX
    VALUEPART1                         0200000608000000XXXX

  • The difference between FIELD-SYMBOL and normal DATA TYPE

    Dear experts,
    Please see the example below, both are output the same result.
    DATA: EXTERNAL_RECORD(4000),
          POSITION TYPE I,
          LENGTH TYPE N,
          ENTRY TYPE STRING.
    EXTERNAL_RECORD = '0005Smith0007Edwards0005Young'.
    DO.
      LENGTH = EXTERNAL_RECORD+POSITION(4).
      IF LENGTH = 0.
        EXIT.
      ENDIF.
      ADD 4 TO POSITION.
      MOVE EXTERNAL_RECORD+POSITION(LENGTH) TO ENTRY.
      WRITE ENTRY.
      ADD LENGTH TO POSITION.
      IF POSITION >= 4000.
        EXIT.
      ENDIF.
    ENDDO.
    --OR It can be written as--
    DATA: EXTERNAL_RECORD(4000),
          POSITION TYPE I,
          LENGTH TYPE N.
    FIELD-SYMBOLS <ENTRY>.
    EXTERNAL_RECORD = '0005Smith0007Edwards0005Young'.
    DO.
      LENGTH = EXTERNAL_RECORD+POSITION(4).
      IF LENGTH = 0.
        EXIT.
      ENDIF.
      ADD 4 TO POSITION.
      ASSIGN EXTERNAL_RECORD+POSITION(LENGTH) TO <ENTRY>.
      WRITE <ENTRY>.
      ADD LENGTH TO POSITION.
      IF POSITION >= 4000.
        EXIT.
      ENDIF.
    ENDDO.
    Is there any special circumstances we need to use FIELD-SYMBOL?
    Why is FIELD-SYMBOL is introduce in the first place?
    Kindly advice with example.
    Thanks in advance for those who can help me on this.

    HI,
    You can use field symbols to make the program more dynamic. In this example the name of a table control is substituted by a field symbol. Thus you cal call the form with any internal table, using the name of the table control as a parameter.
    Example
    form insert_row
    using p_tc_name.
    field-symbols <tc> type cxtab_control. "Table control
    assign (p_tc_name) to <tc>.
    insert 100 lines in table control
    <tc>-lines = 100.
    Field symbols allow you to:
    **     Assign an alias to a data object(for example, a shortened
            name for data objects structured through several hierarchies
            - <fs>-f instead of rec1-rec2-rec3-f)
    **     Set the offset and length for a string variably at runtime
    **     Set a pointer to a data object that you determine at runtime (dynamic ASSIGN)
    **     Adopt or change the type of a field dynamically at runtime
    **     Access components of a structure
    **     (from Release 4.5A) Point to lines of an internal table
            (process internal tables without a separate work area)
    Field symbols in ABAP are similar to pointers in other programming
    languages. However, pointers (as used in PASCAL or C) differ from ABAP
    field symbols in their reference syntax.
    The statement ASSIGN f to <fs> assigns the field f to field
    symbol <fs>. The field symbol <fs> then "points" to the
    contents of field f at runtime. This means that all changes to the
    contents of f are visible in <fs> and vice versa. You declare
    the field symbol <fs> using the statement FIELD-SYMBOLS: <fs>.
    Reference syntax
    Programming languages such as PASCAL and C use a dereferencing symbol
    to indicate the difference between a reference and the object to which
    it refers; so PASCAL would use p^ for a pointer instead of p, C would
    use *p instead of p. ABAP does not have any such dereferencing symbol.
    **     In PASCAL or C, if you assign a pointer p1 to a pointer p2,
    you force p1 to point to the object to which p2 refers (reference semantics).
    **     In ABAP, if you assign a field symbol <fs1> to a field
    symbol <fs2>, <fs1> takes the value of the data object to
    which <fs2> refers (value semantics).
    **     Field symbols in ABAP are always dereferenced, that is,
    they always access the referenced data object. If you want to
    change the reference yourself in ABAP, you can use the ASSIGN statement
    to assign field symbol <fs1> to field symbol <fs2>.
    Using field symbols
    You declare field symbols using the FIELD-SYMBOLS statement.
    They may be declared either with or without a specific type.
    At runtime you assign a field to the field symbol using the ASSIGN
    statement. All of the operations on the field symbol act on the field
    assigned to it.
    When you assign a field to an untyped field symbol, the field symbol
    adopts the type of the field. If, on the other hand, you want to assign
    a field to a typed field symbol, the type of the field and that of the
    field symbol must be compatible.
    A field symbol can point to any data object and from Release 4.5A,
    they can also point to lines of internal tables.
    The brackets (<>) are part of the syntax.
    Use the expression <fs> IS ASSIGNED to find out whether the field
    symbol <fs> is assigned to a field.
    The statement UNASSIGN <fs> sets the field symbol <fs> so
    that it points to nothing. The logical expression <fs>
    IS ASSIGNED is then false. The corresponding negative expression
    is IF NOT <fs> IS ASSIGNED.
    An unassigned field symbol <fs> behaves as a constant with
    type C(1) and initial value SPACE.
    MOVE <fs>
    TO dest     Transfers the initial value SPACE to the variable dest
    MOVE 'A' to <fs>     
    Not possible, since <fs> is a constant
    (runtime error).
    To lift a type restriction, use the CASTING addition in the
    ASSIGN statement. The data object is then interpreted as though
    it had the data type of the field symbol. You can also do this
    with untyped field symbols using the CASTING TYPE <type> addition.
    The danger with pointers is that they may point to invalid areas.
    This danger is not so acute in ABAP, because the language does not
    use address arithmetic (for example, in other languages, pointer p
    might point to address 1024. After the statement p = p + 10, it would
    point to the address 1034). However, the danger does still exist, and
    memory protection violations lead to runtime errors.
    A pointer in ABAP may not point beyond a segment boundary. ABAP does
    not have one large address space, but rather a set of segments.
    Each of the following has its own segment:
    *     All global data
    *     All local data
    *     Each table work area (TABLES)
    *     Each COMMON PART
    You should only let field symbols move within an elementary field or
    structure where ABAP allows you to assign both within the global data
    and beyond a field boundary.
    Rgds
    Umakanth

  • Regd autherisation code for a field

    Hi All,
    i have one user-exit requirement in VA01 . in va01 i need to provide the autherisation on ORDER-REASION field.
    ex:in order resion field F4 (have 5 option there, autherised user need to secect one then document saved else it will the error.
    based on my autherisaion code basis will create a role and they will assign the users.
    is there any special code to provide autherisations for users.

    Something like this (not sure if I get your requirement):
    Authorization Check in ABAP Programs
    A more sophisticated, user-programmed authorization check is possible using the Authority-Check statement. It allows you to check the entries in the user master record for specific authorization objects against any other values. Therefore, if a transaction or program is not sufficiently protected or not every user that is authorized to use the program can also execute all the actions, this statement must be used.
    AUTHORITY-CHECK OBJECT object
                            ID name1 FIELD f1
                            ID name2 FIELD f2
                            ID namen FIELD fn.
    object is the name of an authorization object. With name1, name2 ... , and so on, you must list all fields of the authorization object object. With  f1, f2 ... , and so on, you must specify the values that the system is to check against the entries in the relevant authorization of the user master record. The AUTHORITY-CHECK statement searches for the specified object in the user profile and checks the useru2019s authorizations for all values of f1, f2 ... . You can avoid checking a field name1, name2 ... by replacing FIELD f1  FIELD f2 with DUMMY.
    After the FIELD addition, you can only specify an elementary field, not a selection table. However, there are function modules available that execute the AUTHORITY-CHECK statement for all values of selection tables. The AUTHORITY-CHECK statement is supported by a statement pattern.
    Only if the user has all authorizations, is the return value sy-subrc of the AUTHORITY-CHECK statement set to 0. The most important return values are:
    ·        0: The user has an authorization for all specified values.
    ·        4: The user does not have the authorization.
    ·        8: The number of specified fields is incorrect.
    ·        12: The specified authorization object does not exist.
    A list of all possible return values is available in the ABAP keyword documentation. The content of sy-subrc has to be closely examined to ascertain the result of the authorization check and react accordingly.
    REPORT demo_authorithy_check.
    PARAMETERS pa_carr LIKE sflight-carrid.
    DATA wa_flights LIKE demo_focc.
    AT SELECTION-SCREEN.
      AUTHORITY-CHECK OBJECT 'S_CARRID'
                      ID 'CARRID' FIELD pa_carr
                      ID 'ACTVT' FIELD '03'.
      IF sy-subrc = 4.
        MESSAGE e045(sabapdocu) WITH pa_carr.
      ELSEIF sy-subrc <> 0.
        MESSAGE e184(sabapdocu) WITH text-010.
      ENDIF.
    START-OF-SELECTION.
      SELECT  carrid connid fldate seatsmax seatsocc
        FROM  sflight
        INTO  CORRESPONDING FIELDS OF wa_flights
        WHERE carrid = pa_carr.
        WRITE: / wa_flights-carrid,
                 wa_flights-connid,
                 wa_flights-fldate,
                 wa_flights-seatsmax,
                 wa_flights-seatsocc.
      ENDSELECT.
    In this example, the system checks with the authorization object S_CARRID whether or not the user has a display authorization (03) for the airline entered on a selection screen. If this is not the case, or a different error occurs, the Selection Screen Processing goes back to the display of the selection screen.

  • Re:invalid partial field access: negative offset

    Hi,
           iam getting error invalid partial field access: negative offset, what is this mean

    negative off set not allowed
    Access Using Offset and Length Specifications
    Offset and length specifications are generally critical since the length of each character is platform-dependent. As a result, it is initially unclear as to whether the byte unit or the character unit is referred to in mixed structures. This forced us to put in place certain considerable restrictions. However, access using offset or length specifications is still possible to the degree described in the following. The tasks subject to this rule include accessing single fields and structures, passing parameters to subroutines and working with field symbols.
    Single field access
    Offset- or length-based access is supported for character-type single fields, strings and single fields of types X and XSTRING. For character-type fields and fields of type STRING, offset and length are interpreted on a character-by-character basis. Only for types X and XSTRING, the values for offset and length are interpreted in bytes.
    Structure access
    Offset- or length-based access to structured fields is a programming technique that should be avoided. This access type results in errors if both character and non-character-type components exist in the area identified by offset and length.
    Offset- or length-based access to structures is only permitted in a UP if the structures are flat and the offset/length specification includes only character-type fields from the beginning of the structure. The example below shows a structure with character-type and non-character-type fields. Its definition in the ABAP program and the resulting assignment in the main memory is as follows:
    BEGIN OF STRUC,
      a(3)  TYPE C,   "Length: 3 characters
      b(4)  TYPE N,   "Length:  4 characters
      c     TYPE D,   "Length:  8 characters
      d     TYPE T,   "Length:  6 characters
      e     TYPE F,   "Length:  8 bytes
      f(26) TYPE C,   "Length: 28 characters
      g(4)  TYPE X,   "Length: 2 bytes
    END OF STRUC.
    Internally, the fragment view contains four fragments. Offset- or length-based access in this case is only possible in the first fragment. Statements like struc(21) or struc7(14) are accepted by the ABAP interpreter and treated like a single field of type C. By contrast, struc57(2) access is now only allowed in an NUP. If offset-/length-based access to a structure is permitted, both the offset and length specifications are generally interpreted as characters in a UP.
    Passing parameters to subroutines
    Up to now, parameter passing with PERFORM has allowed you to use cross-field offset and length specifications. In future, this will no longer be allowed in a UP. In a UP, offset and length-based access beyond field boundaries returns a syntax or runtime error. For example, access types c15 or c5(10) would trigger such an error for a ten-digit C field c.
    If only an offset but no length is specified for a parameter, the entire length of the field instead of the remaining length was previously used for access. As a result, parameter specifications are cross-field if you use only an offset, and therefore trigger a syntax error in a UP. PERFORM test USING c+5 is consequently not permitted.
    In addition, in a UP, you can continue to specify the remaining length starting from the offset off for parameters using the form field+off(*).
    Ranges for offset and length access when using field symbols
    A UP ensures that offset- or length-based access with ASSIGN is only permitted within a predefined range. Normally, this range corresponds to the field boundaries in case of elementary fields or, in case of flat structures, to the purely character-type starting fragment. Using a special RANGE addition for ASSIGN, you can expand the range beyond these boundaries.
    Field symbols are assigned a range allowed for offset/length specifications. If the source of an ASSIGN statement is specified using a field symbol, the target field symbol adopts the range of the source. If not explicitly specified otherwise, the RANGE is determined as follows:
    ASSIGN feld TO <f>.
    In a UP, the field boundaries of field are assigned to <fs> as the range, where field is no field symbol.
    ASSIGN <g> TO <f>.
    <fs2> adopts the range of <fs1>.
    ASSIGN elfeld+off(len) TO <f>.
    In a UP, the field boundaries of the elementary field elfield are assigned to <fs> as the range.
    ASSIGN <elfld>+off(len) TO <f>.
    <fs> adopts the range of the elementary field <elfield>.
    ASSIGN struc+off(len) TO <f>.
    ASSIGN <struc>+off(len) TO <f>.
    In a UP, the purely character-type starting section of the flat structures struc or <struc> determines the range boundaries.
    If the assignment to the field symbol is not possible because the offset or length specification exceeds the range permitted, the field symbol is set to UNASSIGNED in a UP. Other checks such as type or alignment checks return a runtime error in a UP. As a rule, offset and length specifications are counted in characters for data types C, N, D, and T as well as for flat structures, and in bytes in all other cases.
    Offset without length specification when using field symbols
    Up to now, ASSIGN field+off TO <fs> has shown the special behavior that the field length instead of the remaining length of field was used if only an offset but not length was specified. Since an ASSIGN with a cross-field offset is therefore problematic under Unicode, you must observe the following rules:
    As previously, the field length of field is used as the length. Using ASSIGN field+off(*)... you can explicitly specify the remaining length.
    ASSIGN <fs1>+off TO <fs2> is only permitted if the runtime type of <fs1> is flat and elementary, that is, C, N, D, T (offset in characters), or X (offset in bytes).
    ASSIGN field+off TO <fs2> is generally forbidden from a syntactical point of view since any offset <> 0 would cause the range to be exceeded. Exceptions are cases in which a RANGE addition is used.
    These rules enable you also in future to pass a field symbol through an elementary field using ASSIGN <fs>+n TO <fs>, as it is the case in a loop, for example.
    Processing Sections of Strings
    You can address a section of a string in any statement in which non-numeric elementary ABAP types or structures that do not contain internal tables occur using the following syntax:
    <f>[+<o>][(<l>)]
    By specifying an offset <o> and a length (<l>) directly after the field name <f>, you can address the part of the field starting at position <o>1 with length <l> as though it were an independent data object. The data type and length of the string section are as follows:
    Original field
    Section
    Data type
    Data type
    Length
    C
    C
    <l>
    D
    N
    <l>
    N
    N
    <l>
    T
    N
    <l>
    X
    X
    <l>
    Structure
    C
    <l>
    If you do not specify the length <l>, you address the section of the field from <o> to the end of the field. If the offset and length combination that you specify leads to an invalid section of the field (for example, exceeding the length of the original field), a syntax or runtime error occurs. You cannot use offset and length to address a literal or a text symbol.
    You should take particular care when addressing components of structures. To ensure the correct platform-specific alignment of type I and F components, they may contain filler fields, whose lengths you need to consider when calculating the correct offset. Furthermore, SAP plans to convert the internal representation of character types to UNICODE, in which one character will no longer occupy one byte, but instead two or four. Although offset and length specifications can work for character fields (types C, D, N, and T) or for hexadecimal fields (type X), incompatible changes may occur in structures containing a mixture of numeric, character, and hexadecimal fields. SAP therefore recommends that you do not use offset and length to address components of structures.
    In nearly all cases, you must specify offset <o> and length <l> as numeric literals without a preceding sign. You may specify them dynamically in the following cases:
    When assigning values using MOVE or the assignment operator
    When assigning values with WRITE TO
    When assigning field symbols using ASSIGN.
    When passing actual parameters to subroutines in the PERFORM statement.
    DATA TIME TYPE T VALUE '172545'.
    WRITE TIME.
    WRITE / TIME+2(2).
    CLEAR TIME+2(4).
    WRITE / TIME.
    The output appears as follows:
    172545
    25
    170000
    First, the minutes are selected by specifying an offset in the WRITE statement. Then, the minutes and seconds are set to their initial values by specifying an offset in the clear statement.
    Offset and Length Specifications in the MOVE Statement
    For the MOVE statement, the syntax for specifying offset and length is as follows:
    MOVE <f1>[<o1>][(<l1>)] TO <f2>[<o2>][(<l2>)].
    Or, when you use the assignment operator:
    <f2>[<o2>][(<l2>)] = <f1>[<o1>][(<l1>)].
    The contents of the part of the field <f1> which begins at position <o1>1 and has a length of <l1> are assigned to field <f2>, where they overwrite the section which begins at position <o2>1 and has a length of <l2>.
    In the MOVE statement, all offset and length specifications can be variables. This also applies to statements with the assignment operator, as long as these can also be written as MOVE statements. In statements where no field name is specified after the assignment operator, (for example, in Numeric Operations), all offset and length specifications must be unsigned number literals.
    SAP recommends that you assign values with offset and length specifications only between non-numeric fields. With numeric fields, the results can be meaningless.
    DATA: F1(8) VALUE 'ABCDEFGH',
    F2(20) VALUE '12345678901234567890'.
    F26(5) = F13(5).
    In this example, the assignment operator functions as follows:
    DATA: F1(8) VALUE 'ABCDEFGH',
    F2(8).
    DATA: O TYPE I VALUE 2,
    L TYPE I VALUE 4.
    MOVE F1 TO F2. WRITE F2.
    MOVE F1+O(L) TO F2. WRITE / F2.
    MOVE F1 TO F2+O(L). WRITE / F2.
    CLEAR F2.
    MOVE F1 TO F2+O(L). WRITE / F2.
    MOVE F1O(L) TO F2O(L). WRITE / F2.
    This produces the following output:
    ABCDEFGH
    CDEF
    CDABCD
    ABCD
    CDEF
    First, the contents of F1 are assigned to F2 without offset specifications. Then, the same happens for F1 with offset and length specification. The next three MOVE statements overwrite the contents of F2 with offset 2. Note that F2 is filled with spaces on the right, in accordance with the conversion rule for source type C.
    Offset and Length Specifications in the WRITE TO Statement
    For the WRITE TO statement, the syntax for specifying offset and length is as follows:
    WRITE <f1>[<o1>][(<l1>)] TO <f2>[<o2>][(<l2>)].
    The contents of the part of the field <f1> which begins at position <o1>1 and has a length of <l1> are converted to a character field and assigned to field <f2>, where they overwrite the section which begins at position <o2>1 and has a length of <l2>.
    In the WRITE TO statement, the offset and length specifications of the target field can be variables. The offset and length of the target field must be numeric literals without a preceding sign.
    DATA: STRING(20),
    NUMBER(8) TYPE C VALUE '123456',
    OFFSET TYPE I VALUE 8,
    LENGTH TYPE I VALUE 12.
    WRITE NUMBER(6) TO STRING+OFFSET(LENGTH) LEFT-JUSTIFIED.
    WRITE: / STRING.
    CLEAR STRING.
    WRITE NUMBER(6) TO STRING+OFFSET(LENGTH) CENTERED.
    WRITE: / STRING.
    CLEAR STRING.
    WRITE NUMBER TO STRING+OFFSET(LENGTH) RIGHT-JUSTIFIED.
    WRITE: / STRING.
    CLEAR STRING.
    This produces the following output:
    123456
    123456
    123456
    The first six characters of the field NUMBER are written left-justified, centered, and right-justified into the last 12 characters of the field STRING.

  • AFS-BW Report on Multi Store Orders (MSO)

    Hi Everyone,
    We have a Sales Doc Type "ZMSO" Multi Store Order and when exploded
    creates many "ZSSO" Single Store Orders.
    In my BW report i need to show all Unexploaded Multi Store Orders (ZMSO) Quantity and Value.
    But in my Sales Cubes i dont find Multi Store Orders, i can find Single Store Orders (ZSSO).
    I checked in VBAK and there are Multi Store Orders in this table, then why ONLY the documents with Type = ZMSO not extracted into BW.
    Have anyone had this issue ? Any reasons for why we cannot extract Multi Store Orders ?
    Thanks and Regards,
    Naveen Rao Kattela

    Hi Suman,
    follows the elementary fields and their corresponding in BW.
    Name
    Data Element
    No. of Characters
    Corresponding InfoObjects
    AFS: Color
    /AFS/BWEL_COLOR
    8
    0AF_COLOR
    AFS: Size
    /AFS/BWEL_SIZE
    8
    0AF_SIZE
    AFS: Country
    /AFS/BWEL_COUNTRY
    3
    0AF_COUN
    AFS: Stock Quality
    /AFS/BWEL_QUAL_STC
    3
    0AF_SQUAL
    AFS: Requirement Quality
    /AFS/BWEL_QUAL_REQ
    3
    0AF_RQUAL
    Hope this help you

  • AFS Valuation

    Hi ,
    iam working in textile industry ..here we are using AFS package , in mm02 iam facing one problem ..in mm02 at AFS valuation tab when iam entering the new valuation data ...it is throwing the error like "*Dimensions/category fields overlap in mapping to elementary fields".*plase help me...
    regards
    vishnu

    For split valuation with category X it becomes like batch valuation and valuation type is same as batch. For materials which are split valuation but not category X that is batch valuation, you can manage the material in batches and default valuation type there in transaction code MSC1n and if not batch managed then in Tc  OMWc.
    Regards

  • Any AFS experience

    Hi,buddies:
       Is there anybody has experience about AFS solution?such as Nike and ADIDAS,is there business content for AFS or I have to enhance all related datasource so that I can extract AFS specific data,such as size XXL etc.
       See you in the point panel.
    Martin

    hi Martin ,
    In AFS you have datasources which are specific to AFS in the business content if you see in the industry specific solutions you will find AFS specific conetent
    and regarding your doubt about picking the sizes in AFS like L, M, S, XL, XXL- they are in the infoobject 0AF_GRDVAL,
    One of the difference from AFS and Standard is that in AFS as you have elementary fields and have infoobjects like Size, color, ..etc.
    i think i am clear.
    and also the filling of setup tables for inventory is a bit different you won't be using the standard BX instead you have to go through a procedure it is described in OSS,,,right now i don't have it with me...so kindly check in OSS.
    and their is also a procedure explained in the OSS how the standard datasources are transformed into the AFS specific.
    i hope that this information is a bit helpful to you.
    thanks and regards
    NEEL

  • How to change the billing qty directly during VF01 in AFS?

    Dear experts:
       Can anyone advise how we can change the billing qty directly during VF01 in AFS? Can anybody tell me why i can modify the billing qty in SAP R/3 ECC6.0, but it fail to in AFS, why?
    The operation was:
    1、I have  to done one customising, in VOV7 for my Item category change the Billing Relevance to "K"；
    2、We setting up as Delivery note  related billing and would like to change the qty at the point of billing；
    3、Enter the Delivery note number Do not Press Enter, Then Click on u201Cselection listu201D, however , the field of "open quantity"  is in greyed out mode !
    In SAP R/3 ECC6.0 ,In transaction VF01 put the Delivery note NO. and before entering or executing go to "selection list" and we will find the quantities in editable mode and we can change there and then execute billing,but in AFS,the field of "open quantity"  is in greyed out mode ! I asked a lot of friends in AFS, they also  have this problem!
    Thanks
    Peter.lee
    Edited by: peter.lee on Nov 19, 2011 3:05 AM

    Hi Guys,
    Contrary to others IS (retail, oil etc...), AFS has been almost fully redesigned in some areas. That's why SAP releases first EHP business functions for standard and then try to enhanced the new created features later in AFS EHP.
    In regards to the change of the billing quantity, from my prospective this is not supported. Quantity always comes from preceding document.
    AFS is implemented in many industries like workwear, fashion high fashion, sportwear, underwear, bags etc...However I never got the same requirement to change the billing quantity.
    For which reasons do you need to change the billing quantity ? Can this be done in the sales order (in case of debit/credit memo request) or in the delivery ?
    The billing area has some restrictions, such as doing a pricing redetermination, in AFS it must be done in the sales order for example.
    You could potentially ask SAP and see whether an advanced modification could be provided (this is chargeable).
    Hope this might help.
    Regards,
    Mehdi

  • BW AFS in Productive State

    Greetings,
    I am interested in anyone to share their experiences in a live BW AFS environment.  Specifically, we understand that clients do convey different levels of customizations, making some of them unique.  But, from a more general Industry Specific (AFS) perspective: to what degree has our SAP BI Content satisfy general reporting requirements?  What has been the major challenges? (Data loading/scheduling, tracking production orders, contracts, etc.)  Best Practices in AFS reporting/Analytics examples, lessons learned that could be applied to other AFS customers.
    Assumptions:
    BW 3.x, or NW04s
    DI 4.70
    ECC 5.0
    Netweaver
    All input from your experiences will be properly rewarded with SDN points.
    Thank you in advance.
    Joseph Banegas

    Hi Naveen,
    You can find the information on AFS (datatargets, infosources, datasources, keyfigures and characters...) in the following link...
    http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/27443cbe062e59e10000000a114084/frameset.htm
    Only schedule line level datasouces have AFS specific fields as the size color... is the information at schedule line level. If you want to report at higher level you can just go with the normal item level or header level extractors
    Hope it helps

  • Stock using AFS (2LIS_03_BX and 2LIS_03_BF)

    Hi,
    I have enhanced 2LIS_03_BF and 2LIS_03_UM extractors with AFS-specific fields, according to note 458676.
    But the note do not enhance 2LIS_03_BX with AFS-specific fields.
    <b>
    Can I use 2LIS_03_BX to do opening stock balance to enhanced BF extractor?</b>
    (must I enhance BX? )
    Taki

    You must check if the new fields are required for the initial inventory....try toload and check....
    In this PDF file you can find how to handle inventory management scenarios
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    Regards
    Message was edited by:
            Oscar Díaz

  • Differnces

    difference b/w AT NEW <field> and ON CHANGE OF <field>

    on-change
    Syntax
    ON CHANGE OF <f> [OR <f1> OR <f2>...].
    Opens an ON control structure, which ends with ENDON. The statement block is executed whenever the contents of the field <f> or one of the other fields <fi> has changed since the statement was last executed.
    At-NEW.
    AT for group change
    Change of group when processing loops of extracts and internal tables.
    Syntax
    AT NEW <f>.
    AT END OF <f>.
    AT FIRST.
    AT LAST.
    AT <fg>.
    The statements are used to process group levels within a loop using an extract dataset or an internal table. They introduce statement blocks that must be closed with ENDAT. The statements between AT and ENDAT are only executed if the corresponding group change occurred.
    On change - should not use in new version.
    The Major Difference is :
    a) When AT NEW occurs,
    the alpha-numeric fields have ******* in their value,
    b) where as in case of ON CHANGE,
    the alpha-numeric fields have their corresponding value,
    of that particular record,
    where the Event gets fired.
    Other differences are :
    ON CHANGE OF can be used any where in the program..
    on change of differs from at new in the following respects:
    1.It can be used in any loop construct, not just loop at. For example, it can be used within select and endselect, do and enddo, or while and endwhile, as well as inside get events.
    2.A single on change of can be triggered by a change within one or more fields named after of and separated by or. These fields can be elementary fields or field strings. If you are within a loop, these fields do not have to belong to the loop.
    3.When used within a loop, a change in a field to the left of the control level does not trigger a control break.
    4.When used within a loop, fields to the right still contain their original values; they are not changed to contain zeros or asterisks.
    5.You can use else between on change of and endon.
    6.You can use it with loop at it where . . ..
    7.You can use sum with on change of. It sums all numeric fields except the one(s) named after of.
    8.Any values changed within on change of remain changed after endon. The contents of the header line are not restored as they are for at and endat.
    while
    AT NEW can be used only within a loop of an INTERNAL TABLE..
    5. Sample program to get the taste of it
    (just copy paste)
    6.
    REPORT ABC.
    DATA : BEGIN OF ITAB OCCURS 0,
    bukrs like t001-bukrs,
    f1(10) type c,
    end of itab.
    itab-bukrs = '1000'.
    itab-f1 = '1111111'.
    append itab.
    itab-bukrs = '1100'.
    itab-f1 = '3333333'.
    append itab.
    itab-bukrs = '1200'.
    itab-f1 = '555555'.
    append itab.
    AT NEW
    loop at itab.
    at new bukrs.
    write :/ itab-bukrs , itab-f1.
    endat.
    endloop.
    AT ONCHANGE
    loop at itab.
    ON CHANGE OF ITAB-BUKRS.
    write :/ itab-bukrs , itab-f1.
    ENDON.
    endloop.
    Thanks
    Seshu

Maybe you are looking for