Billing Request in Value Contract Document Type

Dear Friends
In Value Contract Document Type WK1 in [VOV8] Billing Request is IRC:- Debit Memo Request for Contract
What is the use of it how i will see it is effect in standard business process
Regards
Arun

The billing request is your call off sales document for the value contract e.g. USD 2,000 contract for which initially only USD 500 is billed, thus the debit memo request. The process applies to a situtaion where there is/are partial or staggered releases of contracted goods or services.

Similar Messages

You cannot view this document (Contract Document Type)

Hello!
I have a problem a with a Workflow Definition because I appear the following Error in the log (Setup > System Administration > System Management > System Information > Logs)
u201CYou cannot view this document (Contract Document Type) because you do not have the appropriate permission. Contact the system administrator and request permission.u201D
This happens when I change the status of a Draft to Draft Review. specifically, within the prescript code occurs when you run the line of code:
typeBean = typeHome.find(doc.getDocTypeReference());
The Prescript code within XPDL it is the next:
import com.frictionless.api.common.exception.*;
import com.frictionless.api.common.log.Logger;
import com.frictionless.api.common.platform.*;
import com.frictionless.api.common.types.*;
import com.frictionless.api.doc.collaboration.*;
import com.frictionless.api.doccommon.masterdata.*;
import com.frictionless.api.ibean.*;
import com.frictionless.api.util.*;
import com.frictionless.api.workflow.*;
import com.frictionless.api.projects.*;
import com.frictionless.api.common.log.*;
import com.frictionless.api.ibean.*;
import com.frictionless.api.usermgmt.masterdata.*;
import com.frictionless.api.doc.collaboration.*;
import com.frictionless.api.doccommon.doc.contract.*;logMsg = Logger.createLogMessage(session);
logMsg.setLogMessage("KCSM ENG Signal Material - Draft Review");
Logger.info(logMsg);
typeHome = IBeanHomeLocator.lookup(session, doc.getDocTypeReference());
typeBean = typeHome.find(doc.getDocTypeReference()); // here appear the error.
u2026
Can you help because this error and above all how to solve
thanks

Hello!
I have a problem a with a Workflow Definition because I appear the following Error in the log (Setup > System Administration > System Management > System Information > Logs)
u201CYou cannot view this document (Contract Document Type) because you do not have the appropriate permission. Contact the system administrator and request permission.u201D
This happens when I change the status of a Draft to Draft Review. specifically, within the prescript code occurs when you run the line of code:
typeBean = typeHome.find(doc.getDocTypeReference());
The Prescript code within XPDL it is the next:
import com.frictionless.api.common.exception.*;
import com.frictionless.api.common.log.Logger;
import com.frictionless.api.common.platform.*;
import com.frictionless.api.common.types.*;
import com.frictionless.api.doc.collaboration.*;
import com.frictionless.api.doccommon.masterdata.*;
import com.frictionless.api.ibean.*;
import com.frictionless.api.util.*;
import com.frictionless.api.workflow.*;
import com.frictionless.api.projects.*;
import com.frictionless.api.common.log.*;
import com.frictionless.api.ibean.*;
import com.frictionless.api.usermgmt.masterdata.*;
import com.frictionless.api.doc.collaboration.*;
import com.frictionless.api.doccommon.doc.contract.*;logMsg = Logger.createLogMessage(session);
logMsg.setLogMessage("KCSM ENG Signal Material - Draft Review");
Logger.info(logMsg);
typeHome = IBeanHomeLocator.lookup(session, doc.getDocTypeReference());
typeBean = typeHome.find(doc.getDocTypeReference()); // here appear the error.
u2026
Can you help because this error and above all how to solve
thanks

Method to get contract document type in prephase

Hi All,
Which method can be used to get contract document type in prephase change script?
How to find these methods?
Regards,
Prabhat

Hi
getDocTypeReference() will get you the reference type of contract doc. Use this reference ID to locate the Home API and find the contract type using findUniqueReferenceByName()
Regards
Mudit Saini

Service contracts & document types

Can anyone provide insight on how to setup document types using P40040 for service contracts. For amortization of fixed price contracts, are you using service contracts

Hi
please check this in path
Spro-Financial accounting-Financial accounting globe setting-tax on sales or on purchase-Basic Setting-Check calculation procedure-Define Procedure
Here check taxinn procedure you have define use stander TAXINN or create ZTAXINN
and check which condition has define there, analysis that which goes to g/l account and which goes to inventory
Regards
Kailas Ugale

Purchase condition based on Contract document type

Dear Gurus,
We have created a seperate documents for Domestic and Import Contracts. We want to trigger Domestic Pricing condition in Domestic Contract, and vise verse... We want only the domestic condition to apprear in the dropdown when the purchase team is creating a domestic contract. Does Condition sequencing provide any means to achive this?
Waiting for a reply.
Regards
VPV

>
VIKAT verlekar wrote:
> Dear Gurus,
>
> We have created a seperate documents for Domestic and Import Contracts. We want to trigger Domestic Pricing condition in Domestic Contract, and vise verse... We want only the domestic condition to apprear in the dropdown when the purchase team is creating a domestic contract. Does Condition sequencing provide any means to achive this?
>
> Waiting for a reply.
>
> Regards
>
> VPV
Separate calculation schema are created for both domestic and import and they are attached to vendor. When vendor is inputted in the contract, vendor is the determining factor of which calculation schema it should bring as attached in the vendor. So only conditions attached with vendor will be bought once vendor is entered in contract. It can be either local or import.

Billing request with reference to contract

Hey guys,
I had problem while creating the Billing request (DP91) with reference to the service contract and the folliwing messages are encountering:
1. Copying from sales document type ZTNM (contract document type) to ZTNM is not supported.
2. Procedure: if you wnat to copying ZTNM to ZTNM to be allowed. you must add the entries in copying control.
Please give me the clear picture why I am facing this problem and if i need to maintain the co opy control which doc. to which document i need to maintain.
I would apprciate for your prompt responses and please do the needfull.
Thanks
ANGKS

Hi,
Not clear about ur query..still..go to VOV8 enter ur contract doc.type(ZTNM) and check the billing type(DP91) if u have maintained any...
now go to t-code VTFA and check the copy control settings are maintained for them...if not maintain the same..(similar like OR to F1)
Reg
JJ

How to create a billing request for service order that has serv contract?

Dear Experts,
Can you please help me?
The scenario is, my client has service contracts with their customer but they want to charge customers not periorically but as and when they provide service (ad-hoc).
So how to bill the customer in this case?
In my testing if I have a service contract (order type = SC) then when I create service order, system automatically picks up standard order type SM01. (which is service order with contract.)
And when I perform time confirmation and material consumption (goods issue), actual costs gets booked to the service order. However, using the service order number as referece, if I try to create a billing request in DP90, system create a blank billing request with no line items.
So, could you please advice, how can I create a billing request for a service order, if I have a contract?
Appreciate your help.
Best regards,
Abdul Rafey

Hi Praveen,
Thank you very much for your reply. I appreciate your time and efforts.
Ok, these are the steps how I have executed the process.
- I have created a service contract for an equipment. In the service contract, I have maintained the service material in the line item, maintained price and assigned equipment in the technical objects.
- I created service notification, which automatically picked up contract.
- When I create service order, from notification screen, system automatically picked up correct order type SM01 (Service order with contract).
- Then I planned operations and spare parts in the service order.
- Checked settlement rule in the service order is SDI.
- released and saved service order.
- Using IW42, in SAP ECC6, you can perform both time confirmation and material consumption using the same screen and also TECO service order. System issues message to say, goods issue have been posted.
- when you check the document flow of service order, you can see operations posted, and also goods issue posted.
- check cost tab to see actual costs. (if I want to settle costs from service order to service contract, I can do so w/o a problem in KO88)
- Use DP90, enter service order number and create billing request. System takes to billing request screen but it is blank. No line items.
- So, since there is a contract, in this case, am I meant to be creating the billing request from Service contract? instead of from Service order?
I hope I have clarified myself better this time.
Best regards,
Abdul Rafey

How to create release order for value contract?

dear experters,
I create a value contract by T-code:va41, order type"WK1".I set a Assortment module to this order and mateirl "WKM1" to it.
then I create release order by T-code:va01 with refrence to this value contract,but it set the material "WKM1" to the sales order, and I can't modify this material! I want to put another material which belong to the assortment module in the value contract. I want to know how.
thanks.
Best regards
lance

Assortment Module for Value Contracts
This function enables you to define a list of materials that can be released from a value contract. Materials can be assigned to more than one assortment module.
An assortment module is an entry tool and can be called up from the value contract. It is valid for a certain time period.
If you delete a material from the assortment module, to which a value contract refers, you will be unable to release that material.
In the value contract, only materials with the same sales organization and distribution channel as the value contract can be taken from the assortment module. All the other materials in the assortment module are not displayed in the value contract.
To fulfill both these requirements, two types of value contracts are offered in the standard system:
Value contract type WK 1
You can specify a product hierarchy or a assortment module for value contracts with contract type WK 1. The system will always propose this type of contract, if you want to create a contract for several materials or a certain group of materials. All the materials in the relevant assortment, or belonging to the specified product hierarchy are then relevant for release.
Value contract type WK 2 (material-related)
You can create contracts for one material (usually configurable) with this type of value contract. A software company is an example of where this kind of contract is often used. There, a contract for the value of $500,000 is made with the customer for one specific software product.
You can also agree on the length of the contract for this type. The contract duration can be agreed at item level and can be different from the contract duration specified at header level.
You can store special price agreements for the value contract. These price agreements can then be used at any level. For example, a value contract can contain prices for individual materials, or discounts that are valid for every released material.
Release Orders
The customer fulfills a contract by issuing orders against the contract. The contract does not contain any exact dates for deliveries, so you need to create a sales order to release against a value contract.
When a release order is created for the contract, the system automatically updates the released values in the contract. The release order value is calculated from the total of the open order and delivery values, plus the value that has already been billed to the value contract.
The system also updates the released value for subsequent changes (for example, overdelivery of contract release, price changes in the billing document, partial deliveries, returns, rejection of order items, cancellation or reversal of orders, deliveries or billing documents).
You can create a release order in any currency. The system automatically converts this currency into the one agreed upon in the value contract on the pricing date for the contract release order.
Creating Assortment Modules for Value Contracts
Procedure
To create an assortment module, proceed as follows:
1. From the initial screen choose Logistics >Sales and Distribution >Master data.
2.Choose Products >Value contract - Assortment module > Create.
You will then be in the Create assortment module: Initial Screen.
Module type 6 is defined for the value contract.
3. For external number assignment, enter a module number.
You can then use existing modules as a reference by entering the name of the module under reference.
4. Choose Enter.
5. Enter a short description for the module.
6. Enter a validity period for the product proposal.
During a release, the system checks if the release date lies within the validity period.
7. Create the materials that you wish to assign as items to a module.
You can display a list of materials as a product proposal, which you can then copy into the assortment module. To do this, choose Suggest material, enter the selection criteria in the subsequent screen and copy the selected materials to the items. Use Edit > Delete item to delete the materials that you do not want to copy to the assortment module.
8.Save your entries.
Also Please check the copy control in VTAA
Regards,
Anbu

Changing PO Document type layout programatically

Hii,
My requirement is to change the PO Document type layout programetically. We have customized the standard PO Print report and for that we have created one customized style sheet. We have done the same for 4 types of document types : standard, Contract etc. Now while moving our code into another instance we need to set out custom stylesheet template to the corresponding Document type. Any one have any idea how can we do that from backend? We don't want to update the standard tables as Oracle does not support it.
This is very urgent.
Appreciate your help.
Thanks.

Goto OLME --> Define default value for document type
here for T-code MB01 - cahnge to your doc type
Read that documentation for more info

RSA3 Extractor Testing problem importing request selection values

Hi, I am trying to use RSA3 to test an extract and I am trying to pull in the values from an existing request on the BW side. When I specify the request ID it only pulls in 7 values.
The request I am pulling from has 9 values for "Document Type - BLART" and 18 values from "Account - RACCT". When I specify the request ID I am only getting 7 values for BLART and none of the others.
Any ideas why RSA3 wouldn't pull in all of the values?

Hi,
If the Datasource is LO then it will fetch the data Setup tables, so see it properly. See teh below articles about RSA3
Checking the Data using Extractor Checker (RSA3) in ECC Delta Repeat Delta etc...
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/80f4c455-1dc2-2c10-f187-d264838f21b5&overridelayout=true
Data Flow from LBWQ/SMQ1 to RSA7 in ECC and Delta Extraction in BI
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/d-f/data%20flow%20from%20lbwq_smq1%20to%20rsa7%20in%20ecc%20and%20delta%20extraction%20in%20bi.pdf
https://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
Thanks
Reddy

Release of Value contracts

Hi All,
I have plants using a NB (standard) PO type to release against a Value Contracts (ZP).
As per the rules it was stated that it was a must for us to use ZP so the users are forced to use ZM type (custom) PO to release. They were suppose to get an error message if using the wrong PO type code.
We do not want the plant users to see pricing, with ZB type they can not see the pricing, but with NB they do.
I need to change the config to avoid the value contracts to be released as NB type PO's.
This is an issue which is bussiness conern. Please, can someone advice ASAP how to go with the changes.
Thanks,
Shravya

If you're reference the PO to a PR, than you can remove the assingment of the Contract document type to the PR document type, so the users wont be able to create the PO with reference to the Contract with the specific doc type.
SPRO->Materials ManagementPurchasingContract--Define Document Types --> Link purchase requisition - document type

What are the sources system will pick the document type while creating invo

hi
I would like to know how system will pickup the doucment type while creating invoice in vf01.
i have taken off the fields f1, f2, from the document type. in billing sub tab. so The moment when am creating billing system automatically displaying F2 invoice doucment creation. What are the sources for this.
thanks & Regards
Rack129

Hi,
Hope you have maintained u2018Delivery relevant billing type F2u2019 and u2018Order relevant billing type F1u2019 in the billing tab of the Sales document type in VOV8.
If you create delivery related billing, the system will pick F2. This is controlled in Item category (VOV7). Billing relevance in Business data of Item category decides whether this is delivery related or order related. u2018Au2019 for delivery related billing; u2018Bu2019 for order related billing and so on.
Item category is determined by this combination: Sales document type + Item cat group + usage + higher level item cat.
Regards,
K Bharathi

Release orders for value contract

Hi Folks,
I have question on value contract.
Customer contract is fullfilled by issuing orders against the contract. When a release order is created for the contract, the system automatically updates the released values in the contract. The release order value is calculated from the total of the open order and delivery values, plus the value that has already been billed to the value contract. System checks this value with "Outline agreement target value" in value contract and issues warning or error message depends on configuration settings in value contract item catagory.
We have business scenario where system has to check net value of value contract rather than checking "Outline agrrement target value" in value contract. Because we offer some discounts to customer in value contract thus net value of the contract differs from agreement value. So that system will issue error message when release order value exceeds net value of value contract.
Is there any customizing settings available to meet the requirement?
Awaiting for your inputs.
Regards,
Prabhaharan

Hi,
In transcation VTAA at item level have your own cory requirment code which will calcullate net value of the doc, hope this works out
regards
sriky

Configurable Material : error while creating value contract

First snapshot of our Configurable Material 'Material 01'
In MM03 > Basic Data 2
under Client specific configutarion
Cross-Plant CM : (material 01)
Varient (checkbox checked)
In MM03 > MRP1
MRP Type: PD
In MM03 > MRP3
Plant-specific configuration
Configurable Material : Material 01
Varient (checkbox checked)
Planning Varient (checkbox checked)
When we are raising value contract, we are getting error
'Material 01 has status: Configure to Order'
In Item category assignment we have assigned Zw1 (value contract doc type) on lines of 'OR doc' type as follows
SaTy ItCGr Usg   HLevltCA Difftc MltCa
Zw1 0002 blank blank    TAC    TAM
Zw1 0002 blank TAC      TAE
Zw1 0002 blank TAE      TAE
Zw1 0002 blank TAM      TAC
Still we are getting same error .how to resolve this.
Thanks
Rohit

closing...

Defaulting a particular PO document type for a user

Dear Experts,
My requirement is that whenever I execute tranaction ME21N to create a PO, I want the system to default a particular document type (for example..CAPEX PO or Standard PO). In the present scenario, if I dont notice the PO type there are high chances of me creating the PO inder wrong document type.
Is there a solution to this?
Thanks,
Boby Mathew

Hi,
SPROMMPurchasing--Define Default Values for Document Type.
Here maintain doc type against ME21N whichever you want to be defaulted. If ME21N is not there then Just define it and maintain the pur doc type.

Billing Request in Value Contract Document Type

Similar Messages

Maybe you are looking for