Set type COMM_PR_UNIT is not allowed for product type

Hello all, I am working in SRM 7.0 and when I try to replicate service master (DNL_CUST_SRVMAS) I have this error:
Set type COMM_PR_UNIT is not allowed for product type
What can I do? I think that is an ABAP problem
Thanks in advance
Rosa Rodríguez

Rosa,
This note is something different and nothing to do with the issue. Can you share how did you resolve the DNL_CUST_SRVMAS issue? We are also getting same error.
Thanks,
Jagadish

Similar Messages

HR payee type selection is not allowed in production mode

Hi All,
Does anyone has clue with this error 'HR payee type selection is not allowed in production mode processing" when i'm creating third party remittance evaluation run (new) PC00_m99_URME. I'm selecting Garnishment & child support payee from drop down as i want to post my garnishment amount through 3PR.
Any response would be needful.
Thanks,
KMM

SAP runs 3rd party remittance eval for a given payroll area / pay period as a whole (i.e. regardless of payee types) when this is run in production mode (i.e. only allows this fields to have values if you run in test mode). Therefore, when run in prod mode, this selection field should not have any values.

Status profile not allowed for object type

hi
i had created a status profile (for having 2 statuses before production order release) and assigned in the order type.
but while creating the production order i receive the following error.
Message no - CO622
status profile not allowed for object type
please provide your inputs
regards
Ramesh

Ramesh,
once you cerate a Status profile in BS02 and add status to the same. in the tollbar you will see OBJECT TYPE push button, select teh obejcts like PP/PM order header / operation /comepeoent and PRT ect where that staus can be applied.
Then assign the statsu profile to order type.

ABAP Dictionary type FLTP is not allowed for screen element

Hi Experts
I tried to open VBFA in se16 and i got the message in the status bar like this , what does it mean. please explain.
"ABAP Dictionary type FLTP is not allowed for screen element"

Hi,
This is from help
ABAP Dictionary type FLTP is not allowed for screen element
Message no. 37048
Diagnosis
The format of the ABAP Dictionary field is only for use within the ABAP
program and cannot be used in the Screen Painter.
Procedure
The field cannot be used in screens. If you want to output the
information in the field or assign a value to the field from the screen,
you must use an intermediate field with an appropriate format.
Reward points
Regards

Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'

Hi All,
I created the wsdl for mobile and I tried to send a SOAP request from Altova XMLSpy. However when I geive the wsdl in 'wsdl file location' I receive the following.
File http://127.0.0.1:8080/B1iXcellerator/exec/dummy/com.sap.b1i.vplatform.scenarios.setup/vPac.sap.B1Mobile/001sap0003_sap.B1Mobile.wsdl is not valid.
Invalid XML schema: 'Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'.'
Error location: wsdl:definitions / wsdl:types / xs:schema / xs:element / @type
Any Idea?
Vangelis

Hi,
it seems that Altove did not cope with defaultNs prefix that is used for marking default namespace.
just look up in your <xs:schema > tag what namespace prefix is used for your namespace - you shall find there something like this
<xs:schema xmlns:ns0="your.namespace.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
and replace prefix defaultNs with prefix of your namespace (in example above it would be ns0)
There might be several usages of defalutNs iside of WSDL (at least in my case were two) so replace it everywhere using same approach
Best regards, Artem

Transaction CLM1 not allowed for notification type QL

Hello guys,
one of our user try to open the transaction CLM1/CLM2/CLM3 he getting error message Transaction CLM1 not allowed for notification type QL
please any one give solution for this issue.
find the error screen shot for your reference.
Thanks
Surya

Hello Surya,
Have you done Basic configuration for Claims processing in SAP Project System.
SPRO > Project System > Claim > Notification - Claim > Notification creation
Also check config for Settings for Claims.
Refer sap help for more details
SAP Library - Claim Management
Regards
Tushar

Transaction QM03 not allowed for notification type MQ

HI Dears,
The following error is appearing when i want to view my notification created through defects
Transaction QM03 not allowed for notification type MQ
How to rectify it ?
Alagesan

Hi,
Check IQS3 transaction also....
Cheers,
Tushar

Down Payments Error: Account type K is not defined for document type DZ T

I am getting the error message: Transaction code: F-29
Account type K is not defined for document type DZ
Message no. F5243
In this case i am trying to post a customer down payment in t.code: F-29.
In the document type DZ in OBA7 we tick only G.L and Customer tab as this is not a vendor document.
Also the settings in T. Code : OBXR where we maintain configuration for customers has been maintained with a special G/L reconciliation account.
any help will be really appreciated,
Regards
Satish

I have checked all the settings
OBXR for Customer Down Payments. It is with indicator A and a Special G/L Account has been configured.
The special G.L Account is of the Recon account type Customers with FSG as Recon accounts
The document type DZ in OBA7 is ticked for G.L and Customer and this is how i think it should be as i am not paying a vendor downpayment
but it still gives me the same error.
Regards
Satish

Error:Account type D is not defined for document type RE

Hi! I encountered this error msg: "Account type D is not defined for document type RE" while posting IR in mir6. What does this error msg mean? Thanks!

hi,
RE stands for Gross postings...
When you block the document for payments...its never possible to the post the payments for such documents...
The invoice seems to get posted, but is internally blocked for payment and later you need to delete the payment block indicator and process the invoice further for payments...
check OMBA as well for the settings...
Regards
Priyanka.P

Account type D is not defined for document type RE - Credit Memo

I tried to key in credit memo of fixed asset at MIRO but prompt out this errors "Account type D is not defined for document type RE". I checked OMBA - account type for vendor is selected. Any advise to resolve this problem?

Hi Sanil,
It is just a debit Vendor and Cerdit Fixed Asset. Is anything wrong here?

Error - Account type D is not defined for document type WL

I am getting error while doing PGI (Post Goods Issue).
Error - Account type D is not defined for document type WL

As we had the same problem for a document in our system, I was also browsing for the answer. I saw this thread and now we have found the solution, so could not resist sharing, although it is an old posting.
In these cases it can be that a user wants to create a purchase order of the type UB. But if you have stock transport between two companies, you should not use this order type. You have to use order type NB.
If the user creates the PO with NB then probably they will not get the message.

Partitioned IOT of Object Type - mapping table not allowed for bitmap index

Hi,
looks like a feature available for standard Partitioned IOTs is not supported for object based tables, namely the MAPPING TABLE construct to support secondary local bitmap indexes.
Can you confirm behaviour is as expected/documented?
If so, is a fix/enhancement to support mapping table for object-based Partitioned IOTs in the pipeline?
Results for partition-wise load using pipelined table function are very good, look-ups across tens of millions of rows are excellent.
Environment = Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
OS = Oracle Enterprise Linux Server release 5.2 (Carthage) 2.6.18 92.el5 (32-bit)
Here's the potted test-case...
1) First the non object based Partitioned IOT - data is range-partitioned across the alphabet
CREATE TABLE IOT_Table (
textData VARCHAR2(10),
numberData NUMBER(10,0),
CONSTRAINT IOT_Table_PK PRIMARY KEY(textData))
ORGANIZATION INDEX MAPPING TABLE PCTFREE 0 TABLESPACE Firewire
PARTITION BY RANGE (textData)
(PARTITION Text_Part_A VALUES LESS THAN ('B') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_B VALUES LESS THAN ('C') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_C VALUES LESS THAN ('D') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_D VALUES LESS THAN ('E') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_E VALUES LESS THAN ('F') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_F VALUES LESS THAN ('G') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_G VALUES LESS THAN ('H') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_H VALUES LESS THAN ('I') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_I VALUES LESS THAN ('J') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_J VALUES LESS THAN ('K') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_K VALUES LESS THAN ('L') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_L VALUES LESS THAN ('M') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_M VALUES LESS THAN ('N') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_N VALUES LESS THAN ('O') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_O VALUES LESS THAN ('P') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_P VALUES LESS THAN ('Q') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Q VALUES LESS THAN ('R') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_R VALUES LESS THAN ('S') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_S VALUES LESS THAN ('T') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_T VALUES LESS THAN ('U') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_U VALUES LESS THAN ('V') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_V VALUES LESS THAN ('W') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_W VALUES LESS THAN ('X') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_X VALUES LESS THAN ('Y') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Y VALUES LESS THAN ('Z') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Z VALUES LESS THAN (MAXVALUE) PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0))
NOLOGGING PARALLEL -- FLASHBACK ARCHIVE IOT_Flashback_Data
SQL> table IOT_TABLE created.
2) Create the local secondary bitmap index utilising the underlying mapping table
CREATE BITMAP INDEX IOT_Table_BMI1 ON IOT_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
SQL> bitmap index IOT_TABLE_BMI1 created.
3) Quick test to confirm all ok
SQL> INSERT INTO IOT_Table VALUES ('ABC123',100);
SQL> 1 rows inserted.
SQL> SELECT * FROM IOT_Table;
TEXTDATA NUMBERDATA
ABC123     100
4) Now create a minimal object type to use as the template for object table
CREATE TYPE IOT_type AS OBJECT
textData VARCHAR2(10 CHAR),
numberData NUMBER(10,0)
) FINAL
SQL> TYPE IOT_type compiled
5) Attempt to create an object-based range partitioned IOT, including MAPPING TABLE clause as per step (1)
CREATE TABLE IOTObj_Table OF IOT_type (textData PRIMARY KEY)
OBJECT IDENTIFIER IS PRIMARY KEY ORGANIZATION INDEX
MAPPING TABLE -- we'd like to use this feature to enable use of Bitmap Indexes...
PCTFREE 0 TABLESPACE Firewire
PARTITION BY RANGE (textData)
(PARTITION Text_Part_A VALUES LESS THAN ('B') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_B VALUES LESS THAN ('C') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_C VALUES LESS THAN ('D') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_D VALUES LESS THAN ('E') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_E VALUES LESS THAN ('F') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_F VALUES LESS THAN ('G') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_G VALUES LESS THAN ('H') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_H VALUES LESS THAN ('I') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_I VALUES LESS THAN ('J') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_J VALUES LESS THAN ('K') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_K VALUES LESS THAN ('L') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_L VALUES LESS THAN ('M') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_M VALUES LESS THAN ('N') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_N VALUES LESS THAN ('O') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_O VALUES LESS THAN ('P') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_P VALUES LESS THAN ('Q') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Q VALUES LESS THAN ('R') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_R VALUES LESS THAN ('S') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_S VALUES LESS THAN ('T') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_T VALUES LESS THAN ('U') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_U VALUES LESS THAN ('V') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_V VALUES LESS THAN ('W') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_W VALUES LESS THAN ('X') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_X VALUES LESS THAN ('Y') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Y VALUES LESS THAN ('Z') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Z VALUES LESS THAN (MAXVALUE) PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0))
NOLOGGING PARALLEL -- FLASHBACK ARCHIVE IOT_Flashback_Data
This errors out with the following...
SQL Error: ORA-25182: feature not currently available for index-organized tables
25182. 00000 - "feature not currently available for index-organized tables"
*Cause:    An attempt was made to use one or more of the following feature(s) not
currently supported for index-organized tables:
CREATE TABLE with LOB/BFILE/VARRAY columns,
partitioning/PARALLEL/CREATE TABLE AS SELECT options,
ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
*Action:   Do not use the disallowed feature(s) in this release.
6) Re-running the create table statement in step 5 without the MAPPING TABLE clause works fine. Not surprisingly an attempt to create a secondary local bitmap index on this table fails as there's no mapping table, like so...
CREATE BITMAP INDEX IOTObj_Table_BMI1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
CREATE TABLE with LOB/BFILE/VARRAY columns,
partitioning/PARALLEL/CREATE TABLE AS SELECT options,
ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
*Action:   Do not use the disallowed feature(s) in this release.
CREATE BITMAP INDEX IOTObj_Table_BMI1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL
Error at Command Line:99 Column:13
Error report:
SQL Error: ORA-00903: invalid table name
00903. 00000 - "invalid table name"
7) Creating a secondary local b-tree index is fine, like so...
SQL> CREATE INDEX IOTObj_Table_I1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
index IOTOBJ_TABLE_I1 created.
8) A quick test to ensure object table ok...
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DEF456',500));
SQL> 1 rows inserted.
SQL> SELECT * FROM IOTObj_Table;
TEXTDATA NUMBERDATA
DEF456     500

Thanks Dan,
the intention is to range partition based on the initial character, so A* -> Text_Part_A, B* -> Text_Part_B, and so on.
Here's an example, using an empty IOTObj_Table as created previously.
1) Set up & confirm some test data (two 'D's, one 'N', and two 'Z's)
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DEF456',500));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DDD111',510));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('N3000',515));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('ZZ1212',520));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530));
SQL> COMMIT;
SQL> SELECT * FROM IOTObj_Table;
TEXTDATA NUMBERDATA
DDD111     510
DEF456     500
N3000     515
Z111X     530
ZZ1212     520
2) Just to prove our IOT is enforcing the Primary Key based on the TextData attribute, try to insert a duplicate
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530));
Error starting at line 141 in command:
INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530))
Error report:
SQL Error: ORA-00001: unique constraint (OCDataSystems.SYS_IOT_TOP_84235) violated
00001. 00000 - "unique constraint (%s.%s) violated"
*Cause:    An UPDATE or INSERT statement attempted to insert a duplicate key.
For Trusted Oracle configured in DBMS MAC mode, you may see
this message if a duplicate entry exists at a different level.
*Action:   Either remove the unique restriction or do not insert the key.
3) Now confirm that our data has been slotted into the range-based partition we expect using the PARTITION clause of SELECT...
- The two 'D's...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_D);
TEXTDATA NUMBERDATA
DDD111     510
DEF456     500
- The single 'N'...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_N);
TEXTDATA NUMBERDATA
N3000     515
- The two 'Z's...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_Z);
TEXTDATA NUMBERDATA
Z111X     530
ZZ1212     520
4) And to wrap up confirm an empty partition
SELECT * FROM IOTObj_Table PARTITION (Text_Part_W);

Setting 'Content Copying' as 'Not Allowed' for offline PDF

Hi,
Can anyone help on the following scenario?
Generate a PDF that does not allow user to copy contents within the PDF.
Setting the Document Restriction - 'Content Copying' as 'Not Allowed'
As this PDF is to be open offline, there will be no direct connection to the livecycle server hence not able to connect to the Rights Management Server to verify the policy.
How can this be achive?
Ryan.

Ryan
You are correct in your understanding. Just to clarify one point though, the client machine does require the "Principal" key be downloaded from the RM server and "Synchronize for offline" is one way to get the key. In addition to this, when a user "authenticates" to the RM server to open a policy protected document, a "synchronization" occurs in the background and if there are "new" principal keys for other policies they will be downloaded even if they are not reklated to the document the user is currently accessing.
Now, in addition to Rights Management, Adobe has two other "encryption" options.
You could password protect the document to prevent "content copying", but this is not a very secure option, password protection is easily cracked, there is no user authentication, and third party PDF viewers may not respect\enforce the password protection.
Another option, which is very secure is to use the "Encrypt with certificates" option, where the PDF is encrypted for a user based on the users x509 certificate (public key). The user then uses their corresponding private key to authenticate themselves and view the document. Encrypt with certificates allows you to enforce authentication and you can allow\deny the same "permissions" that you can with RM protection. There is no requirement for a server, but the "certificate management" (certificate creation\provisioning\revocation) capability requires a PKI. Also, the user will need to have their private key available to open the document.
Hope this helps.
Steve

Account type D is not defined for document type RE

Hi can any one tell me use of the field " Account with vendor" in table LFB1?
Regards

Which field are you speaking about exactly? Can you give its technical name?
Is it LFB1-EIKTO? F1 help for the field:
Short Text
Our account number with the vendor
Definition
This field contains the account number the company is listed under at the vendor.
You work for companyA, your vendor is companyB. At companyB, in companyB's system, companyA is created as a customer, and they define an ID for it (let's say: "123456").

Account type K is not defined for document type WA

Hi, I encountered this while doing movement type 301 - transfer posting plant to plant. What does this mean?
Thanks so much.
Regards,
Paula

Hi,
Intra-Company STO R One Step Method & Two Step method:
Inter Company STO - One step Method:
At Supp.Plant: Stock Acc. BSX is Credited
At. Rec.Plant : Stock Acc. BSX is Debited
If you maintain Std. Pricing (S)at Rec. Plant and if there is any Price Diff., then Price Diff. Acc.( AUM) will be triggered....
Here all the Acc.Doc. will be generated while doing PGI only.....No Acc. Doc. will be generated at GR...
Inter Company STO - Two step Method:
At Supplying .Plant....While doing PGI..:
Stock acc. BSX is Credited
Cost of Goods sold Acc.(VAY) is Debited(+)
At. Receiving Plant While doing GR:
Stock Acc. BSX is Debited(+)
GR/IR Clearing Acc is Credited
If you maintain any Std. Price and if there is any price Diff. then Price Diff. Acc will be triggered...
Regards,
Biju K

Set type COMM_PR_UNIT is not allowed for product type

Similar Messages

Maybe you are looking for