"Document doesnt exists error" in MM while changing purchase order

While creating purchase order document number gets created but when i view the created document in me22 it shows the error "Document doesnot exists".can anyone help me in this issue
Regards,
Ramesh

HI
After creaating order check it in VBAK.
Aditya

Similar Messages

Error in DTW while importing purchase order

Dear Experts,
when trying to import purchase order ( Documents and Documents lines) ends up with an error
key: DocEntry
Reason: Vendor record not found application - defined or object defined error 65171
Please help
Regards
Jijo

i had to possible import data, i add some additional fields. here i attached latest sample data
Documents_lines:-
RecordKey     LineNum     DiscountPercent     ItemCode     UnitPrice     Quantity     TaxCode
RecordKey     LineNum     DiscountPercent     ItemCode     UnitPrice     Quantity     TaxCode
1          2     12.1     8500     1     [email protected]
2          2     12.2     1200     1     [email protected]
3          2     12.3     2200     1     [email protected]
Documents:-
RecordKey     DocEntry     CardCode     DocDate     DocDueDate     DocType
RecordKey     DocEntry     CardCode     DocDate     DocDueDate     DocType
1     2     V01     20090626     20090626     dDocument_Items
2     3     V01     20090626     20090626     dDocument_Items
3     4     V01     20090626     20090626     dDocument_Items
Thank you for you valuable information Kind co operation
Regards
JIjo

Error SG105 when creating/changing Purchase Order

Hi All,
When we are trying to create or change import purchase orders, an error message pops up saying " Enter rate USD / INR rate type for 07.04.2008 in the system settings".
Currently we had upgraded from SAP 4.6C to ECC 6.0.
The exchange rates are maintained valid from 01.04.2008 using T-code OB08.
Could anyone point out the reason for this problem.
Regards
Alo

Hi
there is no exchange rate setting apart from the OB08 setting
Just check the exchange rate type used is maintained or not.
Recheck the dates & currency conversions
Thanks & Regards
kishore

Error in process while creating Purchase order.

Hi,
    We are using ECS ,Purchase order is not getting replicated to backend as we are getting the following error " With non-valuated GR, please also enter GR indicator" .
Appreciate your inputs!!
Thanks
Rakesh.

Hello,
Please check note:1029209 is applied. Could you please deactive badi:BBP_DOC_CHANGE_BADI and test system behavior again.
Please check the following customizing in backend R/3 system.
(Tr:SPRO)
Materials Management
Purchasing
   Account Assignment
    Maintain Account Assignment Categories
Here, please double click "K" and remove flag for fields
"Goods receipt" and "GR non-valuated", after that, please create a new
PO and test system behavior again.
Kind regards,
Gaurav
PLEASE GIVE FULL POINTS FOR USEFUL REPLIES

Error while Changing Purchase Order quantity

Hi experts,
I am doing a BDC so that it should change the invoice quantity by the Received quantity, and also if the received quantity is 0 it should delete that particular Line item. It is doing well for the above, but i am getting stucked in a po number withe following error,
"Quantity delivered differs from qty. invoiced (Function not possible)". Can any one please help me in this issue...
thanks ,
Ajeeth

you can only set a deletion indicator if invoiced quantity and received quantites are equal.
check the PO history in PO item detail , there you can see how much you received and how much was invoiced.
Maybe you missed to clear GR/IR account with MR11

Error received while changing sales order.

Hi All,
while changing sales order we have received error message "An internal program error has occured.See note 44283".
So could you plesae explain me what needs to be done.
Thanks in advance.

To avoid to store inconsistent data in the future, activate the following method of the BADI                           BADI_SD_SALES:
> 1 - Transaction SE18
> 2 - Definition name: BADI_SD_SALES Menu: Implementation -> Overview double-click on implementation: IM_CORE_CHECK
> 3 - Now you will get an overview on the methods and you see also that the implementation IM_CORE_CHECK is inactive
> 4 - Press the change button and activate
This check works in the following way:
> 1 - if the number of items is less than 10 and there is an inconsistency the system will not store the data and an A-message will occur.
> 2 - If the number of items is greater than 10 and less than 50 and there is an inconsistency the data will be stored and an I-message will occur.
> 3 - if the number of items is greater than 50 there is no check because performance.
Edited by: Gerard Magorrian on Aug 6, 2010 4:01 PM

Deleated Valuation Type --Need Error Message while creating Purchase Order

Hi,
In our scenario , i need a message should flash , if enduser by mistake select the deleated valuation type while creating Purchase Order.
In current configuration , it's not there.
Await your expert opinion.
Regards
Shyam Kogta

I investigated this recently in our company and gave this answer:
A deletion flag does not restrict anything. It is just an indicator to tell SAP that you want this record to be deleted with the next archiving run.
The archiving run then checks if a deletion is possible or not.
So you can set such deletion flags long time in advance, even at a moment where you still have inventory.
To block materials from beeing used in business transactions, usually the material and sales status are used. But these statuses can only be set at overall, plant and sales organisation level.
In some transactions SAP issues warning messages if a material has a deletion flag. This messages could be customized to be an error and prevent any business. However, this type of restriction is not designed for our machine, as we use the material and sales status.
Anyhow, there is no message for valuation types that have a deletion flag in procurement area.
There is one for goods receipts (but only for a certain industry solution that is not used by us)
There is one for deliveries ( VL 211 ).
The valuation types are defaulted from customizing to the transaction e.g. purchase order. Or from info record to the PO. So a standard purchase order gets valuation type ABC , while an internal order (production) gets the DEF. Usually there should not be a need to change this valuation type manually.
So the only solution is to archive the material master at valuation type level.
But I guess, you already have POs with that wrong valuation type, which means you have to archive the POs first. It you have already batches with wrong valuation type, then thy have to be archived as well before a material can be archived.
And finally if you had stock in current year, then you can archive your material in year after next year, as SAP archives only materials that have no stock in current and previous year.

Error while saving purchase order

Hi all,
While saving purchase order i am getting the following error.
Syntax error in program SAPLV61A
in include RV64A932
in line 10
Statement"*&"is not defined.check your spelling.
Thanks& Regards,
Hari.

Hi Hari,
I've just encountered the same problem as you have now in your latest post.
Normally the include that you mentioned is a formula condition value include which you can modify but you probably have
to register this object first on the SAP OSS pages to get an Access key to modify it.
After you've obtained a key launch transaction VOFM and comment out the line "TABLES: VBRK, VBAK".
As you see below SAP did exactly the same thing in several other includes.
Include FV64A582
-> is a formula condition value
    tx VOFM
            -> Formulas
     -> Condition Value
     -> Routine number 582
At line 37 I commented out "TABLES: VBRK, VBAK." which is not used
anyway in this include.
On top of that SAP commented out these definitions in several other
includes: eg. FOICH002, FOICH002, OI_LV61ATOI.
If other persons have comments on this topic please respond/advise.
Hari, inform us if this resolved your problem.
Also reward points if my post aided you in resolving your issue.
Thank you for feedback.
Best regards,
Tom Cockaert.

G/L Account Error While doing Purchase Order In ME21N

Hi,
While Doing Purchase Order in ME21N,i am getting the below error.Kindly help me.
G/L account 809001 cannot be used (please correct)
Message no. ME045
Diagnosis
Comparison of the field selection strings from the G/L account 809001 and the account assignment category F reveals that there is an incompatible combination of field selections for the field selection group 'Network'.
The G/L account field selection is stored in table T004F; that for the account assignment is stored in table T162K.
Procedure
Please enter a correct G/L account.
Thanks
Supriya

Hi Supriya,
U will have to check the field status of account assignment category F in tcode OME9 and compare it with the Field status group that is assigned to GL 809001.
Kindly note that the field status has a prority in the following order.
Supress
Display
Required
Optional
Thus if the network field is suppressed in GL field status and option in account assignment category F, then the below error would come.
Regards,
Kiran

Error message while viewing Purchase order summary

Hi all,
we are in 11.5.10.2 , we are getting error message while viewing purchase order "Currency formatting cannot be performed without a currency code".
is it beacuse of currency not popluated in Purchase order?
Verified metalink note - 960504.1
Thanks
Kiran

Hi Kiran,
Verified metalink and other areas but could not get any appropriate solution.
I tried to reproduce the issue in various available environments...but no luck!
My guess would be the datafix/BUG that you have referred in the MOS note 960504.1
Please check with your DBA for this patch in test instance.
Thanks
-Arif.

Change Purchase Order : Document Date

Hi Gurus,
I would like to change Purchase Order: Document Date due to wrong input but I found out this field has been grayed out from change (ME22/ME22N) after save.
Can anyone tell me how to solve this problem?
Thanks & regards,
Loi

Dear Gurus,
Is there is any effect of changing the PO's Document date? What is the usage of PO's Document date, in which area?
If no effect, can I customize the PO: Document Date field through Application transaction variant function?
Pls adivse.
Thanks & regards,
Loi

While creating Purchase order the system is showing error: vendor 200001145

Hi experts,
while creating Purchase order the system is showing error: vendor 200001145 on line 00010 for ctype ZB12 not defined as head office vendor.
Plz give solution for this.
Thanks&Regards
sreenivas

Hi,
Please check vendor schema maintained in the vendor master,. through this condition type arepicking from system
Aboue condition type not mainatained inthe caluation schame ,which you assigend to vendorand purchasing organization
regards
Channa
Edited by: channadodawad on Dec 3, 2009 9:22 AM

BAPI_ALM_ORDER_MAINTAIN associating notification number while Changing the order

Hi,
I am unable to associate the notification with the PM order while changing the order through BAPI_ALM_ORDER_MAINTAIN. The scenario is like following:
Order is already created & Notification is also created.
Now I am populating the Methods table as:
3. Passing the Notification no. in notif_no field of header table and 'X' in notif_no field of header_up table.
In the return table it shows that the order saved successfully but when we check it in IW32, the notification is not associated with it.
Please suggest.

You might have missed some parameters, that is to be passed, means you have mistakenly commented any parameters that is not to be comment, please search in this forum you will get many threads, then see what is missing.

SRM 7.0 Output for changed purchase order documents

Hi all,
if we change purchase orders we like to send a PO output document for changed purchase orders only if we change certain PO fields in header or items.
What is the functionality in PO - Header - Output - Order and Send Immediatelly ? We thought that this function is the solution!
But independent we press the button <Order and Send Immediatelly > or button <Order> the system creates allways an output document in any cases of PO field changes which will be sent to a supplier (fax, email). How we can control that a PO document only will be created in cases we define ?
Kind Regards
Edited by: Hermann-Josef Wessels on Mar 28, 2011 6:53 PM

Hi Jay,
we like to control the output because PO changes for G/L account, cost centre or change from account assigment order to cost centre are not interesting for the supplier and in this cases a PO document should not be sent to the supplier. This was the main reason why we like to use function <Order and Send Immediatelly>.
So I would like to clarify the requirement:
1. Automatic created output document if a new PO will be created
2. Automatic created output document if a PO will be changed but no output if the following fields will be changed:
e.g. for G/L account, cost centre or change from account assigment order to cost centre
So we come back in our discussion to table: BBPV_COMP_FIELDS. There are entries for POO = PO Output and POR = Version comparison for Purchase Order.
Question: Can I use structure name: BBP_PDS_ACC for our requirement. If yes which field-names I have to maintain in detail in this table. If possible I need the entries in detail.
Kind Regards
Edited by: Hermann-Josef Wessels on Mar 30, 2011 9:20 AM

Event : changing purchase order's type in transaction ME21N

Hi all,
I am looking for a user exit or an enhencement to set some abap code when a purchase order's type is changed by the user in transaction ME21N.
Thanks.
Regards,

Hi,
Please find the user exit list below for ME21N. You can try out.
USER EXIT
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMEKO001 Extend communications structure KOMK for pricing
LMEKO002 Extend communications structure KOMP for pricing
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
M06B0003 Number range and document number
M06B0002 Changes to comm. structure for purchase requisition release
Thanks,
Raj

"Document doesnt exists error" in MM while changing purchase order

Similar Messages

Maybe you are looking for