PROBLEM DURING CREATING AN AR INVOICE

Dear Sir,
I am having a problem during creating the AR invoice from the delivery. I am getting the message: (2) Message Sales Employee is Must. I am unable to create AR invoice for this reason. But when i am going to create AR invoice for the same delivery in different numbering series it is saying that Error in Numbering file, restorer it. I am really unable to cope up this problem. Please help me to resolve it asap.
Regards
Anupam

Hi,
Do you have any addtional code in the SP_TransactionNotification? If yes, try removing the code and then try to add the AR Invoice.
Kind Regards,
Jitin
SAP Business One Forum Team

Similar Messages

Problem during creating delivary and PGI

Hello Friends,
I am facing a problem in creating the Delivary document.
The error is "date in item 000010 of document does not exist"
Please help me out.
With Regards
Sharan

Are you sure you posted in the correct forum? if it's related enterprise services and you're having problem with one of them, please clarify. thanks.

PROBLEM DURING CREATING AP INVOICE

DEAR SAP EXPERT,
I AM HAVING A PROBLEM WHEN I AM GOING TO CREATE AN INVOICE FROM THE DELIVERY. ITS IS GIVING ME THE MESSAGE (2) SALES PERSON IS MISSING. BUT THE THING IS THAT I HAVE ALREADY MENTIONED THE SALES PERSON IN SALES PERSON FIELD. PLEASE GIVE ME THE SOLUTION REGARDING THIS. I AM USING SAP B1 2007 PL10. PLEASE REVERT ASAP

Hi,
find this one as what Gordon suggested.
you can check the SP code from your SQL Management Studio with this path Databases -->> NameOfDatabase -->> Programability -->> Stored Procedure -->> SBO_SP_TransactionNotification
from this Stored Procedure you need to find this "(@object_type = '18')" 18 is the Object type for A/P invoices.
hope it helps.
regards,
Fidel

Problem during creating delivery from PO in intra-co stock transport

Hi All,
during the intra co stock transport process between 2 company codes after the PO is saved as the 1st step of the process,im trying to create a delivery wrt the PO in the transaction code VL10B.
this is giving the following errors
1.documet is incomplete:u cannot save the delivery
2.serial number reqt.not satisfied (V50UC-SERIAL),error group:L1
immediate help on this issues will be appreciable.
thanx
vishal degaonkar

to add more information bout the problem.....
we've assigned serial no's during delivery creation which is done manually.as the delivery creation process in VL10B is in the background it is not picking up the serial no's and hence the incompletion error.
is there any other method to create deliveries from purchase orders???

9i - Problem during create DB

I seem to be successfully installed 9i for Linux on Redhat7.1.
I have already prepare some script to create database, so I skipped DB configuration assistant section during OUI installation.
Afterward I want to use "svrmgrl" as usual to run the script, but there is no "svrmgrl" in $ORACLE_HOME/bin. And also, if I can create DB, how can I start the server?
Dose the "dbstart" script in $ORACLE_HOME/bin work? I have take a look in the script, it use "sqldba" to start the DBs but I cannot find "sqldba" in $ORACLE_HOME/bin, what happened?
null

This little script starts the database on my system. As you found out, svrmgrl has been 'deprecated'
The key part of the script is, of course,
sqlplus "/ as sysdba"
lsnrctl start ; sqlplus "/ as sysdba" << _EOF
startup
exit
_EOF
Cheers, Malte
null

Adobe Acrobate XI and SecCommerce SecSigner have a problem during signing of a document, creating/verification of the signature is not possible - solutions?

Adobe Acrobate XI and SecCommerce SecSigner have a problem during signing of a document, creating/verification of the signature is not possible - solutions? SecSigner is not responding.

Well, I contacted SecCommerce about the issue, the response was, that I should sign the file later (afterwards). This is a solution, but not the best in my opinion.
When I sign the document the SecSigner window/Java window appears and freezes. Adobe is not responding. I have to terminate Adobe because the program is not responding.
I only found this support website, so I have realized that this is a User 2 User site, but it was a try to get some help.

Problem In LSMW during creating position

hi all,
my scenrio is i am creating a unit of type O and after this i have to create position for it.
i create a single recording for this. first i create a unit then position will create. but during creating position it will take a object ID of unit. but position has internal range it will assigned internaly but in my case it is taking object id of unit that is been created.
how to get object ID of position???
thanks
Sachin

hi manoj,
thanks for ur answer,
there is one problem, when i m running my lsmw in my system it is running fine. but when i run my lsmw in other system , in my recording , it automatically assigning object id to the field object id which is blank.
i dont know y this is so?
thanks
Sachin

Problem during SAP Solution Manager Migration - create secure store

Hi all,
I have a problem during a migration of my SAP SOLUTION MANAGEER from Linux ORACLE to AIX 6.1 ORACLE 10.2.0.4
Release SOLUTION MANAGER 4.0 KERNEL 700
I have done the export of the database and now i start with the import.
SAPINST stopped at Create Secure Store phase and this is the log of SercureStoreCreate.log file.
Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
Handler1=09001000A1271B80 Handler2=09001000A1269C20
R0=0000000000000000 R1=0FFFFFFFFFFFD460 R2=0000000000000010 R3=0000000000000010
R4=000000000000000B R5=09000000089B70A0 R6=0000000111BBE829 R7=0000000000000018
R8=0000000111C23D58 R9=000000003A470000 R10=0000000111B99CB8 R11=09000000089CD638
R12=0900000008970594 R13=000000011000D0C0 R14=0000000111BBE7B8 R15=0000000110096400
R16=00000001110EC8B0 R17=0000000111C23FD8 R18=09001000A12753A8 R19=0000000000000013
R20=0000000111C23FB8 R21=0000000111BBE848 R22=0000000110096480 R23=0000000000000000
R24=0000000000000000 R25=0000000110001098 R26=0000000110096400 R27=0000000110016870
R28=0000000000000000 R29=07000000001DD260 R30=000000000000000B R31=0000000000000010
IAR=09000000089CD638 LR=00000001108BB6C0 MSR=A00000000000D032 CTR=09000000089CD638
CR=4222422420000004 FPSCR=8202200000000000 XER=2000000482022000
FPR0 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR1 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR2 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR3 4530000000000000 (f: 0.000000, d: 1.934281e+25)
FPR4 4330000000400000 (f: 4194304.000000, d: 4.503600e+15)
FPR5 4330000000000000 (f: 0.000000, d: 4.503600e+15)
FPR6 3fb9999999999999 (f: 2576980480.000000, d: 1.000000e-01)
FPR7 3c63333333333333 (f: 858993472.000000, d: 8.326673e-18)
FPR8 0000000082024000 (f: 2181185536.000000, d: 1.077649e-314)
FPR9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR10 4330000000000000 (f: 0.000000, d: 4.503600e+15)
FPR11 4077f00000000000 (f: 0.000000, d: 3.830000e+02)
FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR13 4071f40000000000 (f: 0.000000, d: 2.872500e+02)
FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/usr/java14_64/jre/bin/libj9jit23.so
Module_base_address=0900000008998000
Target=2_30_20070530_12820_BHdSMr (AIX 6.1)
CPU=ppc64 (4 logical CPUs) (0x80000000 RAM)
JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using '/tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/core.20110907.081216.6947032.dmp'
JVMDUMP010I System Dump written to /tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/core.20110907.081216.6947032.dmp
JVMDUMP007I JVM Requesting Snap Dump using '/tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/Snap0002.20110907.081216.6947032.trc'
JVMDUMP010I Snap Dump written to /tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/Snap0002.20110907.081216.6947032.trc
JVMDUMP007I JVM Requesting Java Dump using '/tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/javacore.20110907.081216.6947032.txt'
JVMDUMP010I Java Dump written to /tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/javacore.20110907.081216.6947032.txt
JVMDUMP013I Processed Dump Event "gpf", detail "".
Could please help me for finishing the migration?
Thanks in advance
Andrea

Hi,
this is the a part of sapinst.log:
ERROR 2011-09-07 10:12:18.24
FCO-00011 The step createSecureStore with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR ( Last error reported by the step :Cannot create the secure store. SOLUTION: See output of log file SecureStoreCreate.log:
Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
Handler1=09001000A1271B80 Handler2=09001000A1269C20
R0=0000000000000000 R1=0FFFFFFFFFFFD460 R2=0000000000000010 R3=0000000000000010
R4=000000000000000B R5=09000000089B70A0 R6=0000000111BBE829 R7=0000000000000018
R8=0000000111C23D58 R9=000000003A470000 R10=0000000111B99CB8 R11=09000000089CD638
R12=0900000008970594 R13=000000011000D0C0 R14=0000000111BBE7B8 R15=0000000110096400
R16=00000001110EC8B0 R17=0000000111C23FD8 R18=09001000A12753A8 R19=0000000000000013
R20=0000000111C23FB8 R21=0000000111BBE848 R22=0000000110096480 R23=0000000000000000
R24=0000000000000000 R25=0000000110001098 R26=0000000110096400 R27=0000000110016870
R28=0000000000000000 R29=07000000001DD260 R30=000000000000000B R31=0000000000000010
IAR=09000000089CD638 LR=00000001108BB6C0 MSR=A00000000000D032 CTR=09000000089CD638
CR=4222422420000004 FPSCR=8202200000000000 XER=2000000482022000
FPR0 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR1 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR2 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR3 4530000000000000 (f: 0.000000, d: 1.934281e+25)
FPR4 4330000000400000 (f: 4194304.000000, d: 4.503600e+15)
FPR5 4330000000000000 (f: 0.000000, d: 4.503600e+15)
FPR6 3fb9999999999999 (f: 2576980480.000000, d: 1.000000e-01)
FPR7 3c63333333333333 (f: 858993472.000000, d: 8.326673e-18)
FPR8 0000000082024000 (f: 2181185536.000000, d: 1.077649e-314)
FPR9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR10 4330000000000000 (f: 0.000000, d: 4.503600e+15)
FPR11 4077f00000000000 (f: 0.000000, d: 3.830000e+02)
FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR13 4071f40000000000 (f: 0.000000, d: 2.872500e+02)
FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/usr/java14_64/jre/bin/libj9jit23.so
Module_base_address=0900000008998000
Target=2_30_20070530_12820_BHdSMr (AIX 6.1)
CPU=ppc64 (4 logical CPUs) (0x80000000 RAM)
JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using '/tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/core.20110907.081216.6947032.dmp'
JVMDUMP010I System Dump written to /tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/core.20110907.081216.6947032.dmp
JVMDUMP007I JVM Requesting Snap Dump using '/tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/Snap0002.20110907.081216.6947032.trc'
JVMDUMP010I Snap Dump written to /tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/Snap0002.20110907.081216.6947032.trc
JVMDUMP007I JVM Requesting Java Dump using '/tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/javacore.20110907.081216.6947032.txt'
JVMDUMP010I Java Dump written to /tmp/sapinst_instdir/SOLMAN/LM/COPY/ORA/SYSTEM/CENTRAL/AS/javacore.20110907.081216.6947032.txt
JVMDUMP013I Processed Dump Event "gpf", detail ""..).
Thanks
Andrea

Creating of incoming invoice automatically when documen info record created

Hi all,
I apologize because I am asking many questions on this forum during the last few weeks, but I have some problems which I can't solve by myself in one project.
So, this time the question is about incoming invoices.
Here is the situation:
When our customer receives incoming invoice (in paper form) we scan it and send it to one Document management system. In that system we verify the invoice and approve it. After that step the document is released to SAP (only the document info record is created and that info record points to the original document (pdf file) in that DMS).
Now the question is:
Is it possible to automatically create incoming invoice (parked) when the document is released to SAP (it+s document info record created) and to create link between these two SAP objects? Basically it means that at the moment when doc. info record is created, the incoming invoice is created (only with mandatory data) and saved (parked).
We need this functionality because our client wants to have the access to original document (pdf file) when he is about to finish the incoming invoice.
So, is it possible to set up some parameters so that incoming invoice is created automatically after the document info record is created, and linked to that document info record?

I was not aware that u have already done coding to create DIR in SAP. In that case u don't need to rely on status triggering, u may create the invoice prior to DIR creation and then link it to the DIR.It can be done in the way u have mentioned. I.e. linking at the time of DIR with BAPI_DOCUMENT_CREATE.
I doubt we have any direct link to Incoming Invoice from DIR. One of the options i can think of is linking DIR to EKPO(Purchase Order Item) which is mentioned in Invoice.
Else u may need to add another object with object table "RBKP"
Following link will help u in creating new Object for development of new screens [http://help.sap.com/saphelp_erp60_sp/helpdata/en/c1/1c31a243c711d1893e0000e8323c4f/frameset.htm]
BAPI_DOCUMENT_CREATE2 is the latest BAPI instead of BAPI_DOCUMENT_CREATE.
Points Appreciated.

Problem in creating IR through BAPI_INCOMINGINVOICE_create BAPI

Hi,
Some problem in creating IR through the BAPI BAPI_INCOMINGINVOICE_create. I am able to see the IR number after executing the BAPI but unable to see the IR number in the table. The IR number is not getting updated in the database table even though we are doing the commit work after executing the BAPI. Could anyone help me out with this error.
Regards,
Ram

First of all I am assuming that you did not get any error in the BAPI return structure (even though you see document number populated).
Secondly, I guess you tested the BAPI with SE37 and did not get any error (functionally there are a number of BAPIs available to post an invoice and it is important to figure out the correct BAPI - e.g. PO, non-PO invoice, invoice as a GL entry only, etc.).
If that is not true (there is some error in posting), since during the BAPI call the next document number is obtained as a first step, you will see the document number but subsequently if for some reason it is not posted, you will see the result as you mentioned (no data in the database).
If you are using correct BAPI and have no errors, then in ABAP program make sure to call 'BAPI_TRANSACTION_COMMIT' after the BAPI call to post invoice.
For non-SAP external system, you need not have to call the commit BAPI but just closing the connection to SAP will help.

Problem Copy control Order to Invoice

Hi All,
I maintained a copy control from order to invoice and in the item category the pricing type is maintained as 'G'(Copy pricing elements unchanged and redetermine taxes). But when I create invoice the condition value for pallet discount is getting recalculated.
There is a requirement for this condition type in the pricing procedure that when the order quantity is greater than the pallet quantity maintained through material master then only the discount should be affected.But when I change the pallet quantity to less than the order quantity,after the order is created and then invoice the order the condition value is going through the requirement and the value is getting changed .
Can anyone tell me why it is recalculating when the invoice is created, it should not reprice the order, but just carry over current pricing to the billing
All useful answers will be rewarded.
Thanks,
Ranjan

hi,
Refer to OSS note 24832:
14.05.2008 Page 1 of 10
Note 24832 - Pricing rules / TVCPF
Note Language: English Version: 27 Validity: Valid from 18.05.2004
Summary
Symptom
Depending on the situation, the system should redetermine conditions or
not. For this, a differentiated control is required, for example:
1. When you create sales orders or billing documents, the condition types
are partially redetermined although you want to copy the values from
the reference document.
2. During other transactions, however, you want to redetermine the
condition types instead of copying them.
3. The 'New pricing' function on the item condition screen
redetermines all new conditions, that means it works with pricing
category 'B'. This is undesirable to a certain extent.
4. The same applies to the 'New pricing' function for the entire sales
order.
The following text will explain some examples for the use of the pricing
type implemented for this purpose (KNPRS):
Example 1 **********************************
You want to copy condition type 'VPRS' from the sales order into the
billing document. You are using pricing type 'G'. However, as a consequence
the value of the VPRS condition in the billing document differs from the
value of the goods issue posting.
Example 2 **********************************
You want to copy condition type 'PI01' (price for intercompany billing)
from the sales order into the billing document. You are using pricing type
'G'.
Example 3 **********************************
The costs 'VPRS' are to be redetermined when copying a credit memo request
from a billing document. This is required if you defined the credit memo
item in such a way that no costs are to be determined. Since the pricing
requirements are no longer checked when copying, you have to proceed as
described above to eliminate the VPRS.
Example 4 **********************************
The 'New pricing' function on the item condition screen is to keep the
manual condition, this means the function should behave like pricing
category 'C'.
Example 5 **********************************
The 'New pricing' function for the entire sales order is to keep the
14.05.2008 Page 2 of 10
Note 24832 - Pricing rules / TVCPF
manual conditions, this means the function should behave like pricing
category 'C'.
Example 6 **********************************
Billing is to be carried out using pricing type 'G'. However, condition
types with condition category 'S' and 'T' (standard price or moving costs)
are also to be redetermined. In the standard system this pricing type
copies those condition types from the sales order.
More Terms
KNPRS, TVCPF, TVCPA
Cause and Prerequisites
The pricing type controls which condition types are redetermined or which
are copied unchanged (however, the items are always revaluated). Below,
you will find a description of the pricing type characteris
Note that the specified standard pricing type characteristics
partly do not exist in older releases, or that the standard
pricing type characteristics may be different in the
individual releases. Therefore, the given consulting note
should not be considered to be exhaustive. It merely serves to
explain the principle of how a pricing type is structured and
how its characteristics can be influenced. The exact
characteristic of a pricing type in the release being used can
be seen directly in the source code of Form routine
KONDITIONSVORSTEP in Main program SAPLV61A.
o 'A' (Copy price components and redetermine scales):
No condition types are redetermined. Only the scaled prices are
adapted due to a changed basis.
o 'B' (Complete new pricing):
Completely new pricing (as if you created a new item), manual
conditions are lost.
Restriction: Condition types which are not determined via condition
technique (for example, condition type 'VPRS' or condition types
with KNTYP = 'G' which are determined using formulas) are NOT
redetermined even if you do not change them manually.
o 'C' (Copy manual pricing elements and redetermine the
others):
Completely new pricing, manual ones are copied.
Caution: Here you have to make sure that all condition types that
can possibly be changed manually have T685A-KMANU = 'C' (Manual
entry has priority) in Customizing. Otherwise, it is possible that
the conditions are displayed twice (automatically and manually) and
that both are active.
o 'D' (Copy pricing elements unchanged):
14.05.2008 Page 3 of 10
Note 24832 - Pricing rules / TVCPF
As in pricing type 'A' but the prices are fixed (no scales are
read). Condition base value and value are redetermined.
o 'E' (Adopt price components and fix values):
As in pricing type 'D' but neither condition base value nor value
are redetermined.
o 'F' (Copy pricing elements, turn value and fix):
Only used within the program.
o 'G' (Copy pricing elements unchanged and redetermine
taxes):
a) The following condition types are redetermined:
- Condition class KOAID = 'D' (Taxes)
- Condition class KOAID = 'C' (Volume-based rebate)
- Condition category KNTYP = 'I' (Intercompany billing
conditions)
- Condition category KNTYP = 'R' (Invoice list conditions)
- Condition category KNTYP = 'L' (Always new when copying)
- Condition category KNTYP = 'G' (Cost conditions)
- Condition category KNTYP = 'E' (Cash discount conditions)
All remaining condition types are dealt with like pricing type 'D'.
In particular, with pricing type 'G', the system does not only
redetermine the taxes but also the cost conditions and the
intercompany billing conditions.
o 'H' (Redetermine freight conditions):
The following condition types are redetermined:
- Condition type KNTYP = 'B' (Delivery costs)
- Condition type KNTYP = 'F' (Freight conditions)
- Condition type KNTYP = 'L' (Always new when copying)
o 'I' (Redetermine rebate conditions):
Rebate conditions and scales are redetermined.
o 'J' (Redetermine confirmed purchase net price/value):
Condition types with condition category KNTYP = 'D' (Confirmed
purchase net price/value) are redetermined.
o 'K' (Adopt price components and costs. Redetermine
14.05.2008 Page 4 of 10
Note 24832 - Pricing rules / TVCPF
taxes):
The following condition types are redetermined:
- Condition class KOAID = 'D' (Taxes)
- Condition class KOAID = 'C' (Rebate)
- Condition category KNTYP = 'R' (Invoice list conditions)
- Condition category KNTYP = 'I' (Price for intercompany billing)
- Condition category KNTYP = 'E' (Volume-based rebate)
o 'M' (Copy pricing elements, turn value):
No conditions are redetermined; during copying, the condition
values are multiplied with -1.
o 'N' (Transfer pricing components unchanged, new cost):
Condition types with condition category KNTYP = 'G' (Cost) are
redetermined.
Please note that this pricing type has NO effect on the invoice
since here the goods issue value from the delivery is usually
directly transferred to pricing. Redetermination of the settlement
price by subsequently reading the material valuation segment when
executing pricing type "N" would result in the fact that the goods
issue value information were irretrievably lost.
This standard behavior can be changed by a modification only. If
required, please contact your local consultant or SAP Remote
Consulting.
o 'O' (Redetermine variant conditions):
Condition types with condition category KNTYP = 'O' (Variants) are
redetermined.
o 'P' (Revaluation only):
The system does not redetermine any conditions; only the
revaluation occurs.
o 'Q' (Redetermine calculation conditions):
Condition types with condition category KNTYP = 'Q' (Costing) are
redetermined.
o 'U' (Redetermine precious metal conditions):
Condition types with condition category KNTYP = 'U'
(Discount/surcharge for precious metals) are redetermined.
Solution
There are two options to change the standard behavior:
14.05.2008 Page 5 of 10
Note 24832 - Pricing rules / TVCPF
1. Set up a new pricing type (for example, 'X') and allocate the pricing
type in the document flow (copying control in the IMG, Customizing
depending on the source and target document type via Transactions
VTAA, VTAF, VTLA, VTLF and VTFF).
2. Change the pricing type used in the standard system.
Procedure
For both purposes, USEREXIT_PRICING_RULE is used in Program RV61AFZA. This
is called after the setup of internal table STEU which defines the behavior
of pricing types.
Example 1 ******************************
Picing type 'X' is to be set in a way that condition 'VPRS' (which has
condition category 'G') is not redetermined during the billing. Otherwise
it behaves as pricing type 'G'.
Up to Release 4.0B, USEREXIT_PRICING_RULE can be implemented as follows:
FORM USEREXIT_PRICING_RULE
STEU-KNPRS = 'X'.
STEU-KNTYP = 'LRIE......'.
IF KOMK-KNUMA IS INITIAL.
STEU-KOAID = 'CD........'.
ELSE.
STEU-KOAID = 'D.........'.
ENDIF.
STEU-MAUEB = ' '.
APPEND STEU.
ENDFORM.
In order to ensure that pricing type 'X' acts exactly like pricing type
'G', the FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA is to be
used in releases lower than Release 4.0A (if you create a document with
reference to another document, this is called: copying control; here, the
MODE is the pricing type):
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'X'.
IF KONV-KSTEU NA 'CEF'.
KONV-KSTEU = 'D'.
ENDIF.
ENDIF.
ENDFORM.
In this case, you should note that the billing document contains a special
rule concerning cost condition 'VPRS'. If the goods issue for the delivery
note to be billed is posted, the value of the goods issue is copied into
condition 'VPRS'. This is hard-coded. You can prevent this by setting the
field TKOMP-WAVWR to zero in include LV60AFZZ,
USEREXIT_PRICING_PREPARE_TKOMP.
In higher releases, pricing type 'K' is also available, which copies the
VPRS of the order to the billing document and does not redetermine it
unless there is no goods issue posting (otherwise, the above-mentioned
special rule applies.)
14.05.2008 Page 6 of 10
Note 24832 - Pricing rules / TVCPF
Example 2 *********************************
Pricing type 'Y' is to be set in a way that this works as pricing type 'G'
but without redetermining the intercompany billing conditions 'PI01' and
'PI02'. They have condition category 'I'.
Changes in program RV61AFZA:
FORM USEREXIT_PRICING_RULE.
STEU-KNPRS = 'Y'.
STEU-KNTYP = 'GLRE.......'.
IF KOMK-KNUMA IS INITIAL.
STEU-KOAID = 'CD........'.
ELSE.
STEU-KOAID = 'D.........'.
ENDIF.
APPEND STEU.
ENDFORM.
In order to ensure that pricing type 'Y' acts exactly like pricing type
'G', the FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA is to be
used:
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'Y'.
IF KONV-KSTEU NA 'CEF'.
KONV-KSTEU = 'D'.
ENDIF.
CLEAR: KONV-SAKN1.
ENDIF.
ENDFORM.
EXAMPLE 3 *********************************
Pricing type 'Z' is to be set in the same way as pricing type 'D', but this
time the costs are to be redetermined. Up to Release 4.5B, you can
implement USEREXIT_PRICING_RULE as follows (as of Release 4.6A, pricing
type 'N' is available for this procedure):
FORM USEREXIT_PRICING_RULE.
STEU-KNPRS = 'Z'.
STEU-KNTYP = 'G.........'.
STEU-KOAID = '..........'.
STEU-MAUEB = ' '.
APPEND STEU.
ENDFORM.
In order to ensure that pricing type 'Z' acts exactly like pricing type
'D', the FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA is to be
used:
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'Z'.
IF KONV-KSTEU NA 'CEF'
KONV-KSTEU = 'D'.
ENDIF.
ENDIF.
14.05.2008 Page 7 of 10
Note 24832 - Pricing rules / TVCPF
ENDFORM.
Note: To correct the problem, you should define your own pricing types. In
some cases, it may be required to change existing pricing types. This is
required if you want to influence the reaction to certain field changes in
the sales order (see Note 26115 for this). This also allows you to
influence the 'New pricing' function in the sales order and billing
document. This function uses pricing type 'B'.
EXAMPLE 4 *********************************
The 'New pricing' function is meant to keep the manual changes. By default,
pricing type B' is called. As of Release 4.5A, however, you have the option
to store another pricing type for this purpose in Customizing of the
pricing procedure (Transaction V/08).
In USEREXIT_CHANGE_PRICING_RULE of program MV61AFZA, you can
replace pricing type 'B' with another pricing type, for
example, 'C' up to Release 4.0B.
FORM USEREXIT_CHANGE_PRICING_RULE USING PRICING_RULE.
IF PRICING_RULE = 'B'.
PRICING_RULE = 'C'.
ENDIF.
ENDFORM.
EXAMPLE 5 **********************************
The 'New pricing' function is to be set for the entire sales order in a way
that manual changes are kept. In the standard system, pricing type 'B' is
called. As of Release 4.5A, however, you have the option to store another
pricing type for this purpose in Customizing of the pricing procedure
(Transaction V/08).
Up to Release 4.0B, a solution is only possible by means of a modification
in program MV45AF0F:
FORM FCODE_KONB.
PERFORM PREISFINDUNG_GESAMT USING CHARB. <<<<<<<<<< delete
PERFORM PREISFINDUNG_GESAMT USING CHARC. <<<<<<<<<< insert
ENDFORM.
FV45PF0P has to be changed in the same way:
FORM PREISFINDUNG_NEU.
Aufruf neue Preisfindung
PERFORM PREISFINDUNG USING CHARB. <<<<<<<<<< delete
PERFORM PREISFINDUNG USING CHARC. <<<<<<<<<< insert
geänderte Informationen in Beleg übernehmen
PERFORM VBAP_BEARBEITEN.
PERFORM VBAP_BEARBEITEN_ENDE.
ENDFORM.
14.05.2008 Page 8 of 10
Note 24832 - Pricing rules / TVCPF
EXAMPLE 6 *********************************
Pricing type 'X' is to be set so that it functions like pricing type 'G',
but also redetermines condition categories 'S' and 'T'.
Change in Program RV61AFZA:
FORM USEREXIT_PRICING_RULE
STEU-KNPRS = 'X'.
STEU-KNTYP = 'GLRIEST...'.
IF KOMK-KNUMA IS INITIAL.
STEU-KOAID = 'CD........'.
ELSE.
STEU-KOAID = 'D.........'.
ENDIF.
STEU-MAUEB = ' '.
APPEND STEU.
ENDFORM.
To ensure that pricing type 'X' behaves exactly like pricing type 'G', use
FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA:
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'X'.
IF KONV-KSTEU NA 'CEF'.
KONV-KSTEU = 'D'.
ENDIF.
ENDIF.
ENDFORM.
Additional information ***********************
You can display the standard behavior of the pricing types in FORM routine
KONDITIONSVORSTEP (up to Release 3.1I in Include LV61AF0K, as of Release
4.0A in Include LV61AA12). There, for each pricing type, a line exists in
internal Table STEU. The fields have the following meaning:
o KNPRS
This is the pricing type used.
o KNTYP
This field contains a positive list of the pricing categories (up
to 10 values can be entered).
o KOAID
This field contains a positive list of the condition classes (up to
10 values can be entered).
o MAUEB
This field specifies whether manual changes should be copied.
o STFKZ
This field contains a positive list of the scale indicators (up to
14.05.2008 Page 9 of 10
Note 24832 - Pricing rules / TVCPF
5 values can be entered).
o NOTYP
This field contains a negative list of the condition categories (up
to 5 values can be entered).
o KDUPL
This field contains a positive list of the structure conditions (up
to 3 values can be entered).
o NOKDUPL
This field contains a negative list of the structure conditions (up
to 3 values can be entered).
o KFKIV
This field specifies whether intercompany billings should be
redetermined ('.' or 'X' can be entered).
o KVARC
This field specifies whether variant conditions should be
redetermined ('.' or 'X' can be entered).
o PRSQU
This field specifies whether the price source should be taken into
account ('.' or SPACE can be entered).
Note that most condition attributes (fields of the XKOMV structure) can
also have the value SPACE. To use the above 'CA' or 'NA' statements in the
IF statements also in these cases as required, you can fill the fields of
the STEU line with a corresponding number of '.' characters. These values
are mainly checked in FORM routine XKOMV_AUFBAUEN_PRUEFEN (up to Release
3.1I in Include LV61AF0X, as of Release 4.0A in Include LV61AA65).
Header Data
Release Status: Released for Customer
Released on: 18.05.2004 13:18:36
Priority: Recommendations/additional info
Category: Consulting
Main Component SD-BF-PR Pricing
The note is not release-dependent.
14.05.2008 Page 10 of 10
Note 24832 - Pricing rules / TVCPF
Support Packages
Support Packages Release Package Name
DIMP 471 SAPKIPME06
Related Notes
Number Short Text
1009170 Date of services rendered in the credit memo process
992808 Pricing type 'T': Redetermine tax conditions only
547570 FAQ: VPRS in pricing
410907 Allowed pricing types BAPISDLS-PRICING III
195094 Manual prices during intercompany billing
117347 Pricing type K modified for condition category L
114756 Customer hierarchy determination for pricing
102961 New pricing type for milestone billing plans
45326 No prices for customer-specific pricing type
26115 Conditions not updated during field change
Award opints if useful.
Regards,
Raghu.
Edited by: Raghuram Saripalli on May 14, 2008 11:12 AM

Error during creating a new class diagram

Hi everbody,
I'm using JDeveloper 10.1.3.3.0 with ADF Faces and Toplink. I'm exposing to an error message in JDeveloper while creating a new class diagram. The error message is shown in dialog and saying "The name of the element can not be set to 'package name' as another element has got the same name in the package". I have controlled the name of the new class diagram. The name is unique in the package. Also I'm creating this new file in the package "tr.com.bilisim.class_diagram" and details part of this error message in dialog also says
"BME-02002 : The name of the element can not be set to 'class_diagram' as another element has got the same name in the package"
"BME-02002 : The name of the element can not be set to 'bilisim as another element has got the same name in the package"
"BME-02002 : The name of the element can not be set to 'com' as another element has got the same name in the package"
"BME-02002 : The name of the element can not be set to 'tr' as another element has got the same name in the package"
As I understand from the error message, during creating a new class diagram from 'new file dialog' also tries to create the directories in relevant package (tr.com.bilisim.class_diagram).
How can I solve this problem? Please urgent help!
best regards...
--baris

-repost
please urgent
--barisk

"Program files" directory problem during Microsoft Office Customization Installer in non-English versions of Windows

We have a document-level customization solution for Word and are experiencing problems during deployment in an environment running on terminal services. The OS (Windows 2012) is English and Word (2013) is non-English (German).
Installation is done into the "Program Files" folder correctly. But when trying to start a word document linked to the specific template. The "Microsoft Office Customization Installer" pops up with the error.
"There was an error during installation"
From: file:///C:/Programme/[CompanyName]/[Productname]/[Productname].vsto
Downloading file:///c:/Programme/[CompanyName]/[Productname]/[Productname].vsto did not succeed.
Exception: ....
System.Deployment.Application.DeploymentDonwloadException: Download file:///C:/Programme/[Companyname]/Productname]/[Productname].vsto did not suceed. ---> System.Net.WebException: Could not find a part of the path 'C:\Programme\[Companyname]\[Productname]\[Productname].vsto'.
---> System.Net.WebException: ...... ---> System.IO.DirectoyNotFoundException......
The problem seems to be that the installer is looking for C:\PROGRAMME instead of C:\PROGRAM FILES. C:\PROGAMME is the German localized name of PROGRAM FILES (http://en.wikipedia.org/wiki/Program_Files).
The installer installs the solution correctly deployed into c:\program files, but when the later a user tries to start it and the Microsoft Office Customization Installer is called, it tries to access the non-existing "c:\programme" folder. This
doesn't exist, because Windows is English.
Is there any thing related to deploying solutions on a platform which has different languages (mixing/matching of OS language and Office language?)
Thank you for your help

Hello,
1. First, I would confirm with you whether you dealt with the localization for your document-level add-in?
2. Did you use this way to define the Create a class that defines the post-deployment action part of Put the document of a solution
onto the end user's computer (document-level customizations only) and did you get the path with Environment.SpecialFolder enum?
To handle this, I would recommend you consider using Environment.SpecialFolder to set that property.
Regards,
Carl
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Acctg document not created for cancellation invoice

Hi all,
We have a vehicle sales order created with payment card. The SO contains one item for vehicle and one item for parts. The items were delivered and invoiced separately. Hence, SO has one vehicle sales invoice (VSI) and one parts sales invoice (PSI).
The standard procedure was to post VSI first before the PSI. Accounting documents have been created when both invoices were posted. However, there was a need to cancel the PSI. When this was done, cancellation invoice was created but there was no accounting document posted for the cancellation.
I tried simulating the scenario in our test server and cancelled VSI 90000081 first before cancelling PSI 90000082 to test if this can be an alternative solution. Cancellation for VSI was posted successfully but error persists for PSI cancellation.
Order 67 06/19/06 Completed
. Delivery 80000081 06/19/06 Being processed
.. Picking request 20060619 06/19/06 Completed
.. GD goods issue:delvy 4900000293 06/19/06 complete
.. Invoice 90000081 06/19/06 Completed
... Accounting document 2000077 06/19/06 partly cleared
.. Invoice cancellation 90000084 06/19/06 Completed
... Accounting document 2000079 06/19/06 partly cleared
. Delivery 80000082 06/19/06 Completed
.. Picking request 20060619 06/19/06 Completed
.. GD goods issue:delvy 4900000294 06/19/06 complete
.. Invoice 90000082 06/19/06 Completed
... Accounting document 2000078 06/19/06 Not cleared
.. Invoice cancellation 90000083 06/19/06
.. Invoice 90000085 06/20/06 Blocked
Accounting status of 90000083 (where error occurs) in VF03->Header->Details is set to K or <b>Accounting document not created (authorization lacking)</b>.
Any inputs? Thanks in advance.

Hello Sheila,
sorry - my first answer was in mistake - Status K means:
"The transaction is processed using payment cards. The order, however, does not contain valid authorization.
This problem occurs in billing documents for follow-up deliveries."
Could you check this ? Last way would be to set a breakpoint into the FM 'RV_ACCOUNTING_DOCUMENT_CREATE'
and trigger this via VF02 -> Release to accounting.
Regards Wolfgang

Excise Invoice being created before standard Invoice is created

Hi
I create a sales order. With reference to the sales order I create a delivery.
With reference to the delivery, in VF02, if I try to create an Invoice, I get the following message - Excise Invoice created for the Invoice 597500041.
I need the standard invoice to be created first and using the Tcode Ji11n I should create the Excise Invoice.
But instead I get the above message.
What settings should I check and correct.

Dear Vaideeson Marap...
As per my understanding of your question
If excise invoice is being created automatically the movement you create the commercial invoice in (vf01) ,you need to remove the check box in "excise invoice during billing " respective excise group.
Please check and revert
Thanks&Regards
Raghu.k

PROBLEM DURING CREATING AN AR INVOICE

Similar Messages

Maybe you are looking for