Contract Type ZK to PO Type Z006 is not allowed

Hi Seniors,
While trying to create PO with doc type Z006 with ref to contract type ZK, it is showing error like
" Contract Type ZK to PO Type Z006 is not allowed "
If i check in SPRO, PO doc.type has been assigned with PR doc.type only not with contract doc.type and vice versa to contract doc.type to PR doc.type not with PO doc.type. How and where PO doc.type and Contract doc.type will directly link in order to check whether it is maintained or not. kindly advise.
Regards,
JanaMM

>
JanaMM wrote:
> Hi,
>
> Its not STO normal PO only. I am generally asking...if a PO is been created with ref to contract...the doc.type of both PO and contract should have been assigned somewhere i guess. Where that will be ?? kindly clear me plz..
> regards,
> janamm
For checking the document type of contract follow: spro>MM>Purchasing>contract>Define document type, here you will see document types created for contract.
For checking the document type of PO follow: spro>MM>Purchasing>Purchase Order>Define document type, here you will see document types created for PO.
Now to find a link between contract and PO, look up document type of contract LINK PURCHASE REQUISITION option, you will see what PR's can be created relating to a contract. Now look up PO document type with the above procedure, which will tell you which Po document is linked with Contract. SAP Standard Po document type is CONTRACT RELEASE ORDER, but if customized, the name or document type can be different.
Hope I am helpfull.

Similar Messages

Error Addition to stock of material A in storage type 002 is not allowed

Dear all,
I am doing GR for PO in WM. During TO creation I am getting this error Addition to stock of material A in storage type 002 is not allowed. Hence no storage bins can be entered. May I know under what scenarios this type error props up?
Thanks in advance,
Prashanth

Please find the explanation in SAP online help:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/c6/f8449d4afa11d182b90000e829fbfe/frameset.htm
SPRO > LE > WM > Master Data > Define Storage Type
Check
- putaway strategy --> V_T3010-STEIN
- addition to existing stock indicastor ---> V_T3010-ZULAG
As you can read in the help, other factoers such as capacity may influence this.
Regards,
Csaba
Edited by: Csaba Szommer on Feb 19, 2010 7:55 AM

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

Document type ZD does not allow you to assign to object MARA

hi ppl,
I have created a Z document type.but its not allowing me to assign in mm02.what might be the problem..? its throwing an error message Document type ZD does not allow you to assign to object MARA.

You need to enable object linking to mara on your new document type. Go to Tcode DC10, select the document type and then go to the object links area. Create a new object link for your document type.

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

ME 013 Document type ZEBP is not allowed with doc. category B (Please check

We are creating shopping cart with specific items using XMA catalogue ME013 message comes
Shopping cart 0001008270 (Preq. 2900000012) : ME 013 Document type ZEBP is not allowed with doc. category B (Please check input)
Is it related to PO Document type configuration in R/3!
Document type ZEBP is not in table T160 (SAP Transaction Control) or Do I need to debug the BAPI_PO_CREATE1.

Hi
Which SRM and R/3 versions are you using ?
Some related useful pointers ->
Error: ME 013 Document type ECPO not allowed with doc. c ategory B
Re: Shopping cart contains error
Error: ME 013 Document type ECPO not allowed with doc. c ategory B
Hope this will definitely help. Do let me know.
Regards
- Atul

JITOM error movement type 000 is not allow (check your entry)

Hello experts,
In transaction JIOM i try to do an ACTION, but the system display below error message.
movement type 000 is not allow (check your entry)
Could you please help me this is very urgent..
Regards!!
Hugo

Hello Hugo,
Can you clarify what the functionality of transaction JIOM is? I am assuming that this is your own transaction? Going from previous cases of error L3001 being raised, this is almost always associated with the creation of TO documents, can you confirm this is correct?
Can you check that the Item category is relevent for picking? (Transaction 0VLP)
Regards
Stephen

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.

I have a full Team subscription to Creative Cloud, but type kit does not allow me to use some fonts. Do I have to pay extra to have more fonts available to me?

I have a full Team subscription to Creative Cloud, but type kit does not allow me to use some fonts. Do I have to pay extra to have more fonts available to me?

Hi drewacg,
I'm sorry that you ran into trouble with this. Are you the administrative contact on your Creative Cloud team subscription? The admin user doesn't receive the same set of services as a full seat, so you will have a Typekit Trial plan instead of the Portfolio plan.
You have the option of upgrading to the Portfolio level, though. If you would like to do that:
1) sign in at https://typekit.com/login with your Adobe ID and password
2) visit typekit.com/plans, and select the "upgrade" option underneath Portfolio
Your Typekit plan upgrade will be billed separately from your Creative Cloud payments. The Portfolio plan is $49.99/year.
I hope that this helps! If you have any questions, please feel free to send your Adobe ID information to [email protected] and we can look into it further for you. Best,
-- liz

The control type xyz is not allowed on this page. The type is not registered as safe.

Hi all,
I have a solution, say My.Solution, I have a project My.Project in that.In that project I have a few features.I added a visual webpart.In the properties of that, I can see that it has a safe control entry for that.I did not rename any namespace or class name.
I just added this webpart to a new feature(which has List Definition and instance) and deployed it.The class name of the visual webpart is Foo and this is in the namespace My.Solution.Foo.
I opened the sharepoint designer and edited the masterpage.I referenced this in masterpage as
<%@ Register TagPrefix="cus" Namespace="My.Solution.Foo" Assembly="My.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=87a45275f2ea36e3" %>
and I added this to the masterpage as
<cus:Foo runat="server" id="customvisualwebpart"/>
After I save in the designer and refresh the browser, I get the error,
The control type 'My.Solution.Foo.Foo' is not allowed on this page. The type is not registered as safe.
I checked the .webpart file and it has the namespace, My.Solution.Foo.Foo. The .spdata has a safecontrol entry too as
<SafeControl Name="SafeControlEntry1" Assembly="$SharePoint.Project.AssemblyFullName$" Namespace="My.Solution.Foo" TypeName="*" IsSafe="true" IsSafeAgainstScript="false" />
The assembly that contains the webpart is alread deployed to the GAC there.
The web.config for that in C:\inetpub\wwwroot\wss\VirtualDirectories\12345 does not have a safe control entry. I don't want to add it there manualy as I don't have access to web.config in prod
Can somebody tell me what is wrong and what I need to do to fix it?

check you package file
http://sharepoint.stackexchange.com/questions/11524/the-type-is-not-registered-as-safe-when-trying-to-add-a-web-part-installed-by
Hope that helps|Amr Fouad|MCTS,MCPD sharePoint 2010

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);

New Document Type Created but not allowing posting under that Document type

Hi Gurus,
I have created new document type 'JV' & assigned number ranges to that document type. But when I started posting the entries under this document type, system has thrown one error 'NO ACCOUNTING TRANSACTION VARIANT ASSIGNED TO FB01/JV'
Now after assigning transaction 000 (unspecified posting) & varaint 0001 to document type JV I can able to post the entry under this document type. (Classify document type for document spitting)
But I am not still sure whether my assignment to this particular document type is correct or not?
What is the basic criteria on the basis of which we have to select this assignment to particular document type?
Thanks
Sonal

What you have defined is correct. Since you are defining the document type jv meant for any type of posting and not restriciting like payments/receipts/vendors/customers.

Doing an ad - I selected Geneva Open type, but when I packaged the ad, it collected Geneva true type which is not allowed.

I'm creating an ad for a newspaper publication that says it only accepts PDFs with Postscript fonts, not accepting True Type fonts. In Illustrator, I had selected the Geneva with the "O" for Open Type. Why when I packaged the ad, Geneva True Type was packaged, if I had selected the Open version in the Type pallet? How do I work around this? I have to make sure that the ad doesn't get rejected. Please help! Thanks.

Hi Monika,
Thanks for the reply. I don't have 2 Georgia installed - I chose the Georgia in Illustrator because it had the "O" and I thought that meant it was an open font, not true type. I guess I don't understand what open means.
I created the ad in Illustrator and saved it as a press-ready PDF file. Then to hand off the files to my client's art department so they could archive, I packaged the illustrator file - that's when I saw the fonts were True Type (Georgia and Arial Narrow). I'm afraid to send the PDF to the publication to have it rejected 0 they don't take True Type, only Postscript. Does this mean I need to create outlines for all the type?

Doing an ad - I selected Georgia Open type, but when I packaged the ad, it collected Georgia true type which is not allowed. Is my open font really true type??

I'm creating an ad for a newspaper publication that says it only accepts PDFs with Postscript fonts, not accepting True Type fonts. In Illustrator, I had selected the Georgia with the "O" for Open Type. Why when I packaged the ad, Georgia True Type was packaged, if I had selected the Open version in the Type pallet? How do I work around this? I have to make sure that the ad doesn't get rejected. Please help! Thanks.

Open Type fonts are just a container which can have either PS or TTF based fonts within it. As long as the font is embedded in the PDF properly, it should work.

Message type W is not allowed here

Hi,
I am trying to change error message : KI235 Account & requires an assignment to a CO object to warning but I am not able to do it.
There are only I (Note in window) & E (error) in OBA5.
Can someone advice me on this matter.

Hi,
Go to transaction code OBA5,
Enter the application area as KI and enter
Go to new entries, enter the message number 235 - Account & requires an assignment to a CO object.
make online and batch as W- Warning. then save.
now you will not get the error, this will be a warning message.
Regards,
Padma

Contract Type ZK to PO Type Z006 is not allowed

Similar Messages

Maybe you are looking for