In FI there are twochecks on Taxcodes:

1. For each tax line containing a certain tax code there must be at least one revenue line with this tax code. Otherwise àn error FF753
2. For each revenue line containing a certain tax tax code there must be a tax line with this tax code. Otherwise àn error FF805

Thesechecks are explained in note 400766.

The most common situation leading to error FF753 iswhenthere are more

taxconditions with differenttaxcodes, and onetax code isnotassigned to

anynot-taxcondition.

The most common situation leading to error FF805 iswhen a taxcondition,

afteritstax code hasbeenassigned to some not-taxconditions, itnot

passed to FI. Thiscouldoccurifitisstatistical, or ifithasconditionvalue

and condition base value zero.

Checklist forbilling plan

206612 Check listforproblems in billing plan (releasedinternally)

Incorrect Settlement periods in periodicbilling plan

75727 Collective noteBilling plan periodicdates (Release 30o-30F)

205242 Collective noteofperiodicbilling plan (Release 30o-46*)

Status ofbillingplans

88633 SD: statusofbillingplans

Performance

357643 Performance bil.doc. Cancellation -  index update (Release 3.1I-46C)

314160 Performance - billing plan

351656 Performance ofbillingplans 

Billing plan withreferencetomilestones

304461 Billing plan dateswithmilestonereference

388463 Unrequiredbilling plan dates in milestones

407738 Update billing plan dateswithmilestonereference

Status

380169 Status overviewbilledquantitybilling plan

Hi all,

I want to share step-by-step configuration guide to create an incompletion log. Incompletion log is simple but effective tool to make sure that user fills all the required data in sales document which will be required in furthr processing.

Incompletion log configuration                                          Author- Dattatreya N R

The incompletion log is a important and simple concept related to SAP Sales and distribution.

The incompletion log reminds you when data important for further processing is missing from the sales document

We can create incompletion logs for the following:

·         Sales document header data

·         Sales document item data

·         Sales document schedule line data

·         Sales activity data

·         Partner data in sales documents, deliveries & sales activities

·         Delivery header data

·         Delivery item data

Configuration steps:

1)      We define status group

2)      Assign this group to different fields maintained in incompletion procedure

3)      Assign this in completion procedure to sales document type

1)     Defining status groups:

You can define status group for your requirement to define status of incomplete documents and it is to be assigned in incompleteness procedure

SPRO | IMG | SD | Basic function | Log of incomplete items | Define status group

Suppose if we consider status group 03. Check boxes for General, billing doc and goods movement are checked. This means that when general information such as PO number, document date OR billing related information such as terms of payment OR goods movement related data such as quantity picked are missing in corresponding sales documents system will give a message to user saying that document is partially incomplete or incomplete.

Then user has to fill the data to make the document status as complete. We can restrict further processing of incomplete status either not allowing the user to save the incomplete document or allowing the document to save but further processing will not be possible.

Ex., We can say that if terms of payment is  not mentioned in sales order then user cannot save sales order. Or user can save the document but delivery cannot be created without payment terms.

2)      Defining incompletion procedures:

SPRO | IMG | SD | Basic functions | Log of incompletion items | Define incompleteness Procedures

Here we will check the fields maintained for incompletion procedure 11

Note: We have assigned Incompletion procedure 11 to sales order.

In the above screen we can see that we have maintained PO number field to be in incompletion procedure and also checked the Warning checkbox. This means whenever we create a sales order the system will check whether PO number is filled in sales order or not, else it will display a warning message while saving order.

3)      Assigning incompletion procedure:

SPRO | IMG | SD | Basic functions | Log of incompletion items | Assign incompleteness Procedures

We can assign incompletion procedure to following documents

We have assigned incompletion procedure number 11 to sales order type OR. So it will check for all the fields maintained in this procedure (Shown in above screen) while saving a sales order.

Information structures in SAP

An information structure is a table of fields from operative applications like sales or purchases and forms the basis for analytics in Logistics information system. It consists of three main parameters – period unit, characteristics and key figures.

• A period unit gives is used to give reference of time like a week, month or year.
• Characteristics are used to specify the range of data viz. company code, plant, sales organization, sales office or material etc. for which data is compiled.
• Key figures are the data like sales volume, sales value etc. that is collected with reference to characteristics and period unit.

• Create Info Structure:

1.  Go to IMG : Logistics General à LIS àLogistics Data Warehouse à Data basis àInformation Structures à Maintain self-defined information structures OR

Use T-Code – MC21, Enter number & description for your information structure, choose application 01, type as standard, enable planning and continue.

2. Choose characteristics from given field catalogs. Choose Sales Org, Distribution Channel, Division, Sold-to-party, Material and/or as required. Copy & Close.

Similarly, choose key figures like order quantity, confirmed quantity, gross weight, Net Weight, Volume, Billed Quantity, Open Orders Quantity etc. as required.

3. Save your information structure.

4. Go to MC24 to create updating for your information structure. Choose update group 1 (SIS: sales document, delivery, billing document) or as required.

5. Create update rules. Double-click on key figures and specify event, update type, source table source field. Choose table and date field for period determination or click on suggest rules. Copy.

Click on rules for characteristics to create update rules of characteristics for each key figure. Specify source tables and fields for each characteristic. Copy.

6. After creating rules for all your key figures, go to Environment in the menu bar and choose activate updating. Double-click your info structure to select                parameters as shown below. Set period split as required and asynchronous updating. Save.

7. Use T-Code LBW0 to connect your info-structure to SAP BW. Input your info-structure, choose set-up LIS environment and execute.

-Next Choose generate data source and execute.

-For Delta updating in LIS choose generate updating and execute.

8. Display your info-structure in MC23. Go to Environment in menu bar and choose update definitions. Status of info-structure is Active.

Set up statistical data for your info structure

  Use T-Code –> SBIW to go to IMG and – go to Perform setup – sales & distribution and run activity Setup for Orders, deliveries, & billing.

9. Choose activity, enter the info structure (S898), give name of the run, date of termination, time of termination, No. of tolerated faulty documents.

Then execute.

10. Go to LBW0. Specify info structure and click ‘generate data source’.

-- Go to Data Source in the menu bar and click on generate.
--Data Source 2LIS_01_S898 has been generated as shown below.

11. Display settings of your information structure in LBW0.

Settings of info structure will be summarized as below:

*******

Karuna Ravuri

Message 108 (or 008 in the case everything happens in pricing prestep) in the pricing analysis

• … indicates that while executing the pricing analysis a condition record has been found for a specific access but no corresponding line exists in XKOMV of that item.
• Line has been deleted manually
• New condition record created/record changed
• Requirement was not fulfilled
• Fields where initial
• Pricing date problem
• Inconsistencies
• KINAK Z(causesdeletionofcondition after calculation)
• Conditionswithconditionclass‚H‘ (due to a speciallogic)

Unfortunatelyiftheproblemis not reproducableitisoften not possibletodeterminetheactualsource.

Hi Team,

Some times we may need to copy price from MM Condition record to SD condition Record. There can be various reasons as mentioned below:

1) In India, Excise calculation Base needs to be kept same for Intra Company STO / Inter Company STO and Billing Document.

2) Base Price needs to be kept same Bet'n STO and Invoice.

3) Certain Discount or Surcharge needs to be copied from MM to SD or Vice Versa.

When first time I tried , I faced difficulty but got successful in the same, so thought to share it with you also.

Below are the steps which I had followed:

1. Created Identical Condition Type in SD and MM. It needs to be identical considering SAP needs controlling point like Condition Class / Calculation Type.

MM Condition Type:

MM Access Sequence:

SD Condition type : (It is identical to MM Condition type, Only Ref. Condition Type field is updated with MM Condition type and Application as Purchasing.)

SD Access Sequence : (Observe here, I have used Same Condition Table which was created in MM., If you will press F4, You will not see those Condition Table but If you will directly enter the same, System will allow MM Condition Table in SD as well.)

SD Pricing Procedure :

2) Maintain Condition Record for MM Condition Type by MEK1 T-Code.

3) Maintain Condition Record for SD Condition type by VK11 with Zero Price. (Why Do we need to maintain this ?? Ans: In SAP For Populating condition value from Other Module condition record, system search that if this condition has been proposed in Pricing or not. That's why we need to maintain Condition record with Zero value so it get's Populated in Pricing.)

4) Create STO and reach till Billing Creation with Standard way. Check the Pricing now in Invoice.

As per above Screenshots, system has called MM Condition record to SD Pricing.

Hope this will useful and Helpful to all.

Regards,

MJ

Manytimes a Sales Document may be updated incorrectly and the status may be out of sync with the attributes in the document.

For example the sales order has been fullydeliverd then also status is showing open or Inprocessing .

Solution is to Run SA38 with report SDVBUK00 which will determine the status again for the document.

Enter Document Number as shown below and Execute

Report SDVBUK00 should definitely not be scheduled daily. Instead it should only be started if required for the correction of an individual document.

Other : A great table/view which shows a combination of header details and status information is VBAKUK.

Thanks.

Hello All,

Normally we pick the Customer Address in Smartforms by taking Address Number from KNA1 & passing the same in ARDC Table. This will give Customer's address as entered in Customer Master Record.

But think of a scenario where User has changed Customer Address in Sales Order & the same need to be printed in Print-Outs. How to ensure that this new (One-time) address is Printed in Sales Document Print-Outs.

Just like system assigns a address number to each Customer Master, similarly whenever the Address is changed in Sales Documents, system stores the new Address in ADRC Table with new Address number.

Ask your ABAPer to include the following logic in Smartform program:

Go to SE16N & Explore Table VBPA

Enter the relevant Sales Document Number & Partner Function & Execute.

Pick the Address Number (ADRNR) & pass the same to ADRC Table to get the changed address.

Also in VBPA the indicator (Address Indicator) – ADRDA is set to E if Address is changed in Sales Document Manually.

This will ensure that system will print the correct address in Sales Document Print-Outs.

Thanks,

Jignesh Mehta

Most of us know the concept of Credit Account in Credit Management, where we can check Credit Limit of another Customer for a particular Customer.

Thus as seen below, for Customer - CGA0* we will check Credit limit of Customer – WM*:

The Credit Account needs to be assigned in Transaction FD32 & generally this is to be done for many Customers at a given point of time.

SAP has given the facility of MASS update for Credit Account in FD32:

On saving the MASS transaction system gives an error message – F4717 - Credit limit can only be maintained with credit account XXXXXX

The reason for this is one SAP Standard setting:

The above code checks that if the Customer’s (for which Credit Account is to be assigned) Credit is not equal to zero & if the Transaction is Batch Input Session (MASS) then it will throw error message.

Meaning to say that if we want to update the Credit Account for Customers in FD32 via MASS Transaction, then Credit limit of the Customer (for which Credit Account is to be assigned) should be ZERO.

Business Requirement: Many time business need to monitor change Log in Tables. From functional, maintainence support point of view it is important if business can track who is making change and change log. 

Here I will  discuss, how can we acivate change log for Y or Z table. Hope it will be useful .

Caution:

• Activate Logging only where it is really necessary,  Activating logging slows down accesses that change the table.
• If  many users access this log table in parallel. This could cause lock situations even though the users are working with different application tables. So decide judicially before activating this.

This  requires Basis and ABAP setting, but knowing this as a functional consultant will be really helpful.

1. T Code: RZ11  Type Parameter name 'rec/client'

Check basis settings allow to record table logging or not. If it is not activated then you may take help of basis team to activate this.

2. T Code SE11: Once RZ11 setting is ok then go to Tcode SE11. Enter Y or Z table name where you want to activate logging.  Go to the technical setting of table. There Log Data change field should be marked to allow change Logging. If it is not flagged then take help of ABAPER to activate this,

3. Tcode SCU3: Now once above settings are active, you will find change log in this Tcode.

Enter Y Table name for which logging activated

Execute and you will be able to see Change log

Regards

Neeraj Lal

Business Requirement: Many times Business require to send certain output directly to external Id of customer, business partner etc. This document discuss those scenario.

I find in SDN some consultants asking this requirement, I hope this document will be helpful.

Here I will discuss solution which I implemeted in my  business process.

Advantage:  Solution can be use to send output to partner email Id. Consultant can enhance functionality based on logic written in routine , may use logic in routine to fetch data from Ztable which gives flexibility.

we are calling function module 'SO_NEW_DOCUMENT_SEND_API1' in this routine. This function module enables to send output to external email ID

Presetting: Basis setting  (Tcode SCOT) should be available to allow output to be sent to external email id. You may use SOSV or SOST to check this.

I consider all other standard settings of output like access , access sequence, routine are known to consultant and i will not discuss these setting here.

T Code: NACE

For sales order output select application V1 and then Click Output Type button:

If it is require to make this output condtion based on access then define access sequence and assign it to output (Standard SAP Access creation).

In Default view tab select:

Dispatch time as per your requirement.

Transmission Medium '5 External Send'

and partner function which require this output.

Now create and assign form routine to output along with print program

You can take help of ABAPER to create program as per your Prnt program and Form Routine.

Here Form Routine is controlling Email.

You can put logic here that how to fetch email Id, if there is any validation check etc.

In my case I am fetching email from HR Master T Code :PA30. Subtype Communication.

You may write your own logic to fetch email

Note: In this routine, we are calling function module 'SO_NEW_DOCUMENT_SEND_API1' . This function module enables to send document.

Now create output condtion record if this output has access sequence based determination.

Trigger output via sales order

T Code: VA01 : Header Output Screen

T Code: PA30, Info type 0105, Sub Type 0010

I have maintained my email ID in PA30, Info type Communication (0105) Sub Type 0010 (Email).

TCode : SOSV  To Check mail is going or not ( This will also require Basis Setting)

Mail is triggered to my external Email ID which is visible in SOSV.

Regards

Neeraj

Hi,

We can send copy of output to our email also in pdf format -

1.Go to SP02

2.select spool request number

3.At the top left -spool request - forward - send using SAPoffice

4. Enter email-ID & copy (for sending in email)

5. Enter SAP user-ID (any user to whom you want to send) & Copy

For checking in user's business workplace -

1. Go to SBWP

2. Check in inbox.

Hope it is useful.

Regards-

Shashank gupta

As a part of this explanation , I have taken sales order creation into consideration and showed the process of debugging using breakpoint instead

of using watch point that we do in common.

T. Code  : VA01

In the above screen shot you can see the error that was triggered and the following screen shots take you through the process of leveraging this error message to find the root cause of this issue.

Enter '/h' in command field to activate Debugging and click enter

If you Execute now using  f8  you will reach your error message point where you can find out your error.

Once you reach the point you need to check the values in kunnr,vkorg,vtweg,spart by double clicking on those fields.

It should now be evident that the issue was a missing combination of the sales area and the  customer.

Any queries or suggestions to this document are welcome.

Regards,

Sambasiva Reddy Gurrala

SAP SD Functional Consultant

In Continution (adding the last section) to the post "Defaulting sales area in VA01" by Mr. G. Lakshmipathi

You often need to enter some default organizational values in SAP. To avoid having to enter these values every time you can create you own defaults and the following way should enable you to do that.

Click on Menu - System - User Profile - Own Data

or use transaction SU3

Click on the Parameters tab and enter the organizational values that you use in your dialy work. For Parameter ID "XUS" enter your own SAP User ID, so when you run some reports where you require to enter your SAP User ID, your User ID that you enter in Parameter will be copied over.

Save your default values. Similarly you can add many default values as Parameters

To identify Parameter ID's:

Should you find whether there are any additional fields that you want to be defaulted, do as described below:

> Place the cursor on the field you want to find out the value of the Parameter ID and press F1

> Click on Technical information icon

> Check the Parameter ID and enter in it the Parameter tab

Excuse if the similar content has already been shared by any fellow member.

Thanks, br,

Sats

Long time ago I have seen a slide in a presentation to explain different terminlogies used on SAP screen. I immensely liked it. I dont remember who has done it or where I saw it, so cant give credit to the one who got this idea but can extend my thanks to him/her. I have made similar one because I often see end users find some of the terminlogy used by SAP consultants are bit difficult espcially when the support is given over phone. Hence I started adding the below slide in some of my training documents during projects or support manuals so that users could understand what I am saying or/and get used to the terminlogy quickly. Hope it helps someone just like it did to me.

The below screen has been made by adding screenshots from different SAP screens.

Thanks, br,

Sats

AFS Two-Date Pricing

1   Overview

Due to the specific needs of the apparel and footwear business, pricing (list price, discounts, surcharges) may need to be determined based on multiple dates. A company may want to provide a more attractive price to their customers who book early in the season window (providing more time to the manufacturer to produce the goods) and take delivery later in the window.  On the other hand, the company may want to provide a less attractive price to a customer who places a last-minute order with rush shipping.

Two-date pricing in SAP AFS allows this to be accomplished.  Rules can be setup which state the dates that should be taken into account when determining pricing.  For example, a customer who orders on or before a specific date and takes delivery on or after another date would receive an additional discount, or a reduced list price.

2   System Setup
2.1 Master Data

         2.1.1 Material Master

Each material master that will function with two-date pricing will require an update.  On the AFS Sales Data tab in the material master, the Pricing indicator must be flagged with value 04 (Two Date Pricing).   This will activate the functionality for that specific material.

         2.1.2 Pricing Condition Records

To maintain condition records for AFS-specific condition types, transactions J3A4 (Create), and J3A5 (Change) should be used.  After populating the selection criteria, on the resulting screen, define the rule which fits your scenario, Date 1, and Date 2 (which act as variables for the rule).  In the example below, the rule states “Order date on or after [Date 1] AND scheduled ship date on or after [Date 2]”.   Only if the rule is met in the sales document will the condition type trigger.

Once the overall rule has been maintained, the value of the pricing condition will be set.  To do so, double-click on the rule, and populate the percentage or value in the bottom half of the screen.

     2.2 Configuration

         2.2.1 Define AFS-Specific Condition Types

Two-date pricing must be activated on a per-condition basis. This ensures that only those pricing conditions that require two-date pricing will trigger based on the rules defined. 

          To flag a pricing condition for Two-date pricing, follow the path: SPRO >> Sales and Distribution >> Basic Functions >> Pricing >> Pricing Control >>           Define AFS-Specific Condition Types

On the resulting screen, find your condition type, and check the box “Two Date Cond.” 

*Note: this cannot be flagged if an access sequence is assigned to the pricing condition in V/06.

        2.2.2 Define AFS Two-Date Pricing

        Now that the pricing condition type has been activated for Two-date pricing, the rules must be set.  Proceed to SPRO >> Sales and Distribution >> Basic

        Functions >> Pricing >> Pricing Control >> Define AFS Two-Date Pricing.  On the resulting screen, you will find a set of pre-defined rules from SAP.  If               they fit your pricing scenario, you can skip this step. 

        If you require a new rule, you will press “New Entries” and start to create a new entry.  You will need to provide a logical description of the rule, along with           the table-field which relates to Date 1 and Date 2.  Additionally, you may need to create a custom routine which contains your required logic to evaluate             these two dates.

Business Place Configuration Steps

The following steps would take you through the configuration steps for the business place for a particular scenario.

This document is written mainly to explain the purpose of business place concept towards having different number ranges for the outgoing documents.

·         Defining (Assigning to Company Code) the Business Place.

·         Assignment of Business Place to the Plant

·         Maintenance of Document Classes

·         Assignment of Document Classes to the Document Type

·         Maintenance of Number Groups

·         Maintenance of Number Ranges

·         Document Class Determination

·         Assign Number Range to the Business Place.

·         Maintain Copying Control for the Billing documents

Defining (Assigning to Company Code) the Business Place.

The business places are considered to be organization units and are created under the company code level.  In the system, creation of the business place happens only by when the company code is being entered.

SPRO Path: IMG à Cross Application Components à General Application FunctionsàCross-Application Document Numbering à Taiwan àDefine Business Places

Please note that the configuration can be maintained under any Country node in SPRO.

Assignment of Business Place to the Plant

In this customizing step, Business Place is assigned to the combination of Plant/Country/Company Code

Maintenance of Document Classes:

Document class is required to make the differentiation in the documents like Credit/Debit memos / Invoices.

Assignment of Document Classes to the Document Type:

In this step, the Accounting document type is being assigned to the document class created in the last step. Here in our case we have taken the standard Accounting document type “R1”.

Maintenance of Number Groups:

In this customizing step, the number groups are maintained. Generally, the number groups are defined in order to maintain your official number ranges. The number group helps in maintaining different number range as per the business requirement.

Maintenance of Number Ranges:

As shown in the below screen print, the number ranges would be maintained under the Number group.

Document Class Determination:

Here, for the combination of Country / region / SD Doc Cat. / Sales area – Document Class needs to be assigned.The same can be maintained through the table maintenance in “J_1IDCLSDET”

Assign Number Range to Business Place:

Conclusion:

With the above configuration we can have different number ranges followed plant-wise for various different documents (Invoice/Debit Memo/Credit Memo).

Please note the number generated through this Business Place setup would be available as part of the “Reference number” field in the billing document and the same would be reflected in the accounting document as well. With the help of form enhancement the Reference number can be printed in the invoice document for meeting legal requirements.

Reference:

https://help.sap.com

dear all

Delivery  shipping condition copy  as shipment shipping  condition

go to SE38 - LXV56U15  here you find the include ZXV56U1  , you must  activate this include then you write below logic

DATA:

BEGIN OF l_last_data,

       vsbed

LIKE vttk-vsbed,      "Shipping condition

*....

*Further data

END OF l_last_data,

BEGIN OF l_is_not_identical,

       vsbed LIKE rv56a-selkz,     "Shipping condition

*....

*Further data

END OF l_is_not_identical,

     l_start_tabix LIKE sy-tabix,

     l_tabix LIKE sy-tabix.

*****************************************************************

* Analyse Data from deliveries

*****************************************************************

CLEAR: l_last_data, l_is_not_identical.

READ TABLE i_xvttp WITH KEY tknum = c_xvttk-tknum

BINARY      SEARCH.

l_start_tabix = sy-tabix.

IF sy-subrc = 0.

LOOP AT i_xvttp FROM l_start_tabix.

     l_tabix = sy-tabix.

IF i_xvttp-tknum NE c_xvttk-tknum. EXIT. ENDIF.

READ TABLE i_xtrlk WITH KEY vbeln = i_xvttp-vbeln

BINARY      SEARCH.

IF sy-subrc = 0.

* Shipping condition

IF l_is_not_identical-vsbed IS INITIAL AND

NOT i_xtrlk-vsbed IS INITIAL. "ignore initial entries

IF l_tabix = l_start_tabix.

           l_last_data-vsbed = i_xtrlk-vsbed.

ELSE.

IF l_last_data-vsbed NE i_xtrlk-vsbed.

             l_is_not_identical-vsbed = 'X'.

ENDIF.

ENDIF.

ENDIF.

ENDIF.

ENDLOOP.

ENDIF.

******************************************************

* Are data identical in all deliveries ?

* Copy only in this case !

******************************************************

* Shipping condition

IF l_is_not_identical-vsbed IS INITIAL.

   c_xvttk-vsbed = l_last_data-vsbed.

ELSE.

*  MESSAGE ID 'ZSD' TYPE 'I' NUMBER 000.

message 'Ship.Cond.not identical-Cannot copy ship.Cond.' type 'I'.

ENDIF.

once apply this , then create the shipment assign the delivery , then comes main screen click on planing then delivery shipping condition copy as a shipment shipping condition .

regards

sankar

dear all

normally you know some t codes only , but sap provide so much of t codes , you find the t code list at a time

just go to SE11 and enter the table TSTC Then click on display Then click on content after just Transaction code level you can give like V*, Z* , like etc you find all t  t code  like V*  t codes total 1860 , same thing you find the all modules another t codes also

When we process the business requirement sometimes it’s difficult to find out right table in particular area, so instead of search all the tables we can limit our search by provide initial two letters.

Go to T-code: SE16N

Type first two letters then put third letter as * then press F4

Will get list of table which related particular segment.

(given only daily used tables)

Hope this will be helpful.

Comments and suggestions are welcome.

Regards,

Krishna.