OTC Flow

Download Link : OTC Flow

OTC Flow

  1. SALES ORDER

Company Code: 4700

Sales Document type: ZOR

Sales Area: 4700/10/10

Screen Shot 1:

Click Enter

Step 2:

Header Level:

  • Enter Sold to party: 1000991
  • Enter Ship to party: 1000991
  • Enter PO Number: Test
  • Enter Payment term: 0001

Item Level:

  • EnterMaterialsinItemLevel:1000309
  • Enter order Qty: 1
  • Enter Plant: 4702
  • Click Enter:

Refer Screen Shot:

GotoItemBilling

EntertheINCOTermsintheItemLevels:CFR(COSTANDFREIGHT)

Click Save

  1. DELIVERY

DeliveryDocumenttype:ZLF

T – Code VL01N

  • Enter Shipping Point: 4702
  • Enter Sales document number:
  • Note:EnterDeliverydate:(DeliverydateshouldbetakenfromSchedulelinesinSalesorder)ReferScreenShotbelow:

Click Enter

Enter Picking Qty & Storage Location:

Click on Post Goods Issue:

  1. BILLING

Billing Document type: F2

T – Code – VF01

Enter Delivery Document number:

Refer Screen Shot Below:

Click Enter

Refer Screen Shot below:

Click Save

Billing Document should be created (Refer Screen Shot below)

Display the Billing document: T – Code – VF03

EntertheBillingDocumentnumberfromtheaboveScreenshot:

Click on Accounting Document tab:

Refer the Screen Shot:

Advertisements

Proposals and Contracts [Sample]

Download Link : Proposals and Contracts Procedure_1

Proposals and Contracts Procedure

Version1.0

 

 

S.No

Description

Version No

Requested By

Authorized By

 

1.

Initial

1.0

NA

 

 

 

 

 

 

 

 

 

 

 


  1. 1.     Objectives

The objective of this procedure is to define and establish the process of generating and submitting proposals, and of reviewing and finalizing contracts.

  1. 2.     Scope

The scope of this procedure applies to all proposals submitted to prospects and contracts finalized with the customers.

  1. 3.     References

 

  1. 4.     Outstanding Issues
  • None
  1. 5.     Responsibilities
  • It is the responsibility of the Project Manager in charge of that account to make business / commercial proposal under the guidance of the Business Development Manager (BDM).
  • The Chief Executive Officer (CEO) / Vice President (VP) / BD Manager as the case maybe, is responsible for pricing policy for the company’s projects and applications, which will be reviewed from time to time. In case of exceptions, where special sanction is required for deviation from standard pricing and technical specifications, any one of them, as may be the case, would give the final approval for the same.
  • BD Team is responsible for
    • Collecting RFP for any required projects
    • Sales of company’s products/projects
    • Generating leads in the company’s business line.
    • Coordinate with client during the initial project phase and whenever required during the life cycle of the project.
    • Primary requirements gathering from client
    • BD team should maintain a list of clients and do follow-up for all Projects with help of Project manager or Project Lead.
  • Project Manager / Project Lead is Responsible for
    • Preparation of project proposal, estimation and forward to the VP for review and approval
    • Coordinate between client and VP during proposal preparation
    • Initial project resource allocation
    • Analyzing of Client requirements to a granular level before the start of a project.
    • Collecting and Analyzing End-User Requirements for the project.
    • Handling Change Request from the clients during project execution.
    • Tracking of Project Profitability and submitting to the Management.
  • The VP prepares the contract based on inputs provided by the PM/PL and the BD Team
  • The Project Manager is responsible for appointing a Project team to be assigned for each customer project which is being executed.
  • During the contract period, VP/PM is responsible for collecting feedback from customer at regular intervals.
  • Project core team should analyze the customer feedback and should report it to the concerned Lead or Project manager.
  1. 6.     Inputs

 

  1. 7.     Outputs
  • Signed Contract

 

  1. 8.     Control Mechanism
  • The VP approves all contracts, as applicable, between the company and external clients.
  • Proper information sharing mechanism should be established to resolve the communication gap between VP/PM and Development Team, so that VP/PM is able to resolve client related issues regarding the project (Project status, Technical issues).

 

  1. 9.     Procedure

 

Proposals

  • A detailed proposal will be prepared by the concerned Project Manager / Lead The proposal addresses the following:
    • The company’s tool proposed for the particular hardware & network operating system and back-end, as applicable, and suggested by the client.
    • Additional technical information, as needed, about topology, networking, architecture etc., if applicable and required.
    • Brief description of the current situation and business needs
    • Client’s Acceptance Criteria for the project
    • List of known gaps, if any, major deviations, as compared to existing templates
    • Price of development tool / software license used (runtime or development version as needed)
    • Price of hardware, operating system and other software if intended to be supplied by  the company
    • Free or charged training and price thereof
    • Free or charged implementation support, if required
    • Arrangement for travel, lodging, boarding of project personnel if any onsite inspection is to be carried out
    • Price of other services, such as Data Entry services, if intended to be supplied by the company’s Payment terms
    • Any exclusions
    • Guarantee and AMC charges
    • Validity of the offer
    • Rates and taxes as applicable
    • Projects teams along with support teams, if applicable and required, will carry out the risk analysis based on known parameters and interaction with the prospects. They may, if required and applicable, suggest the time and cost estimates to be incorporated in the Proposal.
    • The concerned PM/PL will submit the proposal and follow it up periodically.
    • The complete Risk Analysis and Feasibility cum Business Study will be carried out by the Projects Team.
    • The feasibility cum business study will be conducted to make sure that the requirements of the prospect application, as understood at this stage, are within the capabilities of the company to achieve.
    • It could also cover business workflow, Management Information System (MIS) requirements, user groups and types of functional users, interfaces with other systems and document flow, as applicable.
    • The extent of the study will depend upon the technologies and the risks involved (financial, technical human resource as well as time schedule).
    •  It is necessary to carry out the feasibility cum business study before accepting the order, estimation methodology, in cases where the company does not have application templates.
    • The feasibility cum business study report should highlight
      • Feasibility of executing the project/activity in the organization.
      • Risk involved in the proposed project
      • New functionality’s (those which are not available in the existing templates)
      • A hardware and/or software platform where experience within the company is judged to be inadequate and additional training is required.
      • Estimated time frame and estimates
      • Deliverables
      • The VP along with Project Manager Reviews of Contracts and Proposals before it is been delivered.
      • It is in both the company and the customer’s interests to have risks identified. However, the company may choose to exclude some internal risks from the contract.
      • The final agreement to proceed will be given initially by the VP, after formal Presentation of the Proposal and Review risks.
      • The PM/VP clears the review actions and initiates action for amending the contract accordingly.
      • The VP approves the final Contract Review record.
      • The VP maintains the contracts file and sends a copy with the status for every review to the respective Project Manager.
      • If there is any amendment received by the Project team, it will be informed and discussed by relevant teams to look in to commercial aspect of the same. All such changes affecting the Project Documentation will be controlled in the Configuration Management system.
      • The company, for any changes or amendment to the contract will consider the minutes of the review meeting, approved by the customer, as acceptance by the customer.