A set of requirements is complete if and only if it describes all significant requirements of concern to the user, including requirements associated with functionality, performance, design constraints, attributes, or external interfaces.

Just as there is no one right programming language for every application, there is no one right way to develop the more detailed specifications. Different environments call for different techniques, and the requirements managers and requirements writers will probably need to develop a mix of skills suited to various circumstances.

Some people may think that the best way to estimate a project is to have detailed requirements and design information for each feature. They may argue that this is the most professional and accurate way to approach the problem. However, I disagree with this view. I think that it is more important to be able to make quick decisions about the scope of the project without spending too much time and resources on detailed estimates. Why? Because detailed estimates often turn out to be wrong or irrelevant later on, and they create “wasted inventory” that could have been used for more valuable activities. I’d suggest you only do detailed estimates when the schedule allows for it, and when you have a clear understanding of the value and priority of each feature.

Basic Software Development Process:

1. Defining the requirements.
2. Approval.
3. Template designs.
4. Template approval.
5. Coding.
6. Internal release.
7. Testing.
8. Alpha release.
9. Beta release.
10. Project goes live.

This is the process I follow.

SALES & DISTRIBUTION#

(SD)#

Table of Contents#

1. Definition of Sales & Distribution. 2
2. Enterprise Structure. 3
   1. Client 5
   2. Company. 5
   3. Company Code. 6
      1. Create a Fiscal Year Variant 7
      2. Maintain Fiscal Year Variant 7
      3. Assign Company Code to Fiscal Year Variant 8
      4. Posting Periods. 9
      5. Define Variants for Open Posting Periods. 9
      6. Open and Close Posting Periods. 9
      7. Assign Variants to Company Code. 10
      8. Define Document Number Ranges. 10
      9. Define Document Types. 11
      10. Define Tolerance Groups for Employees. 12
      11. Assign User/Tolerance Group. 13
   4. Plant 13
      1. Assign plant to Company Code. 14
   5. Location. 14
   6. Division. 15
   7. Sales Organisation. 15
      1. Assign Sales Organisation to Company Code. 16
   8. Distribution Channel 16
      1. Assign Distribution Channel to Sales Organisation. 17
      2. Set up Sales Area. 18
      3. Assign sales organisation - distribution channel – plant 19
   9. Define Shipping Points. 20
      1. Assign Shipping point to plant 20
      2. Shipping point and goods receiving point determination:
         • Assign Shipping Point 3. Customer Master
   • Creation of Customer Account Group.
   • Create Number Ranges for Customer Accounts.
   • Assign Number Ranges to Customer Account Groups.
   • Define Incompleteness Procedures.
   • Define Order Type.
   • Define Item Category.

Definition of Sales & Distribution#

For the representation of your company structures in the SAP System, different organizational units are available for the areas of sales, shipping and billing. First analyse the structure and process organisation in your company and then compare them with the SAP structures. In the standard version, different organizational elements are defined as examples. In general, these elements are not sufficient for individual demands. Extend the elements accordingly.