Wednesday, April 16, 2014

SAP : Query Simple Tips

Default Query Area in SQ01
-Execute TCode SU3 to set default parameters
-Enter parameter AQW and level the value as blank

Default User Group for Query
- From SQ01 - Use the first toggle icon on the screen
- From SU3 - Enter the parameter ID (AQB) and your user group

Convert Quick Viewer qeury to query
- Create the table joins using TCode SQVI
- Execute the Tcode SQ01 and from menu Environment-Query Areas change Query area to "Standard area-Client Specific" .
- Check the current user group (Appears as title in SQ01), to change the user group use the first toggle icon on the screen and change user group
- Execute the Tcode SQ01 and from menu: "Query- Convert to Quick view", enter the name of the quick view created from SQVI
- Enter the Query name and the infoset name, the user group is defaulted to current.
- If you needed to default the selection fields, create a Variant for the Quick View
- Execute the Tcode SQ01 and enter query name created.
- Click the change button and enter the variant in Special Attributes tab

Change infoset Description
- Execute TCode SQ02
- Enter the infoset name and click Change
- In the change screen, from menu - Goto - Global Properties
- Save and this ask for program regeneration.

Regards
[V]

Wednesday, April 9, 2014

SAP : Maximum number of items in FI reached

Issue

Although you can maintain the max 999 line items in billing document, and we are aware that each line item of billing document must generate two line items (D&C) in the accounting document, the max line items of billing document is less than 500 lines. Considering taxes etc the number of billing lines could be less than 400.
The cause of this issue is because the line item number (BSEG-BUZEI) field  length is defined as (3) numeric positions, and hence can accomodate 999 line items.
Unable to create more than 999 FI line items is a standard restriction due its field length.
          
Solution

1. IMG -> SD -> Billing -> Billing Document -> Country Specific Features -> Maintain Maximum Number of Billing Items.
2. This is where you can define a maximum number of items allowed for all billing documents within a given sales organization.
3. Also in the copying control for order/delivery to billing document at item level under "Data VBRK/VBRP" and maintain routine 006 "Single inv. limited".

Monday, March 31, 2014

SAP : The reference has already been completely copied or rejected

The above error message in my case occurred when trying to create a Contract with reference to a Quotation or Order from a Quote with a production order, meaning the Primary document is a Quotation

Even though if there is no completion rule specified in the item category of the quotation, the system sets it to A because it checks for the order type and Assembly type combination in the Program SAPFV45P.

IF vbak-vbtyp CA vbtyp_agan AND
NOT t459k-mntga IS INITIAL.
vbap-erlre = chara.
ENDIF.

The first check is for order document type, my case it’s B (Quote). Second check t459k-mntga, is to see if there is Production/Planned order.

Satisfying these conditions the VBAP-ERLRE (Completion rule) is set the CHARA (A) and the VBAP table is updated with completion rule A by default.

Regards,
[V]

Friday, March 28, 2014

SAP Requirement Type and Requirement Class determination

Generally speaking we are aware that SAP Make-to-order production is controlled by the requirements type, but what’s mystical in how the requirement type is determined during the sales order processing. I did a little research to understand this process, which seems tricky compared to the some other SD area determination process like item category or schedule line and below are my findings.

Until Release 3.0, the requirements type was determined on the basis of the item category. For this reason, special item categories weree used unti Release 3.0 for controlling make-to-order production. After Release 3.0 the requirements type is determined on the below sequence primarily in the configuration for Production-MRP and Sales and Distribution in secondary.

1. The Strategy group (MRP3 View) in the Material Master,
    a. A Strategy is assigned to the Strategy group, (Tcode OPPT)
    b. The requirement type is assigned to the Strategy, (Tcode OPPS) and if this fails.

2. MRP group (MRP1 View) in the material master record.
    a. If the Strategy group is not maintained in the MRP3 view, the Strategy group
        is determined based on the Plant + MRP group combination (Tcode: OPPR)
    b. Uses step 1 after step 2.b and this if this fails

3. Based on Material type (Tcode: OMIG)

4. Item category and the MRP type
    a. Determination Of Requirement Types Using Transaction (TCode OVZI)

5. Item category only.
    a. Determination Of Requirement Types Using Transaction (TCode OVZI)


Regards,
[V]

Wednesday, October 16, 2013

MS Word : Unexpected symbol in word documents

If you see any unexpected symbol like  [ ¶ ] in the word documents just press Ctrl+Shift+8 (not F8). This shall clear off the symbols.  

Regards,
[V]

Tuesday, October 15, 2013

SAP : View EDI Segment Qualfiers and Actions (QUALF/ACTION)

The EDI segment documentation was very descriptive in SAP 4.6C where the segment 'Qualifiers' and 'Actions' functions were provided in the segment definition. In the later versions this data was missing and I happened to explore a way. My fellow consultants around the globe might have been using this trick but I liked to write on this one and see below for steps.

1. Execute TCode: SE11
2. Select the 'Data Type'  radio button and input the Segment name for instance E1EDP01.
3. Click the display and you can view the Component and the Component type details
4. Double click on the Component type respective to the QUALF or ACTION elements.
5. This displays the Domain as many of you know.
6. Once again double click on the Domain and go to the value range tab to view the details,

Regards,
[V]