Skip to main content
Solved

Error on attaching document - Field [KEY_REF] is mandatory for category and requires a value

I
Do Gooder (Employee)
Forum|alt.badge.img+4

Hi,

Could someone explain the reason for receiving the following error message when trying to add attachments to the PO No Part Lines.

Product Version: 22.2.7

I have checked the  object connection transformations related to this and found a Object Connection Transformation which does not exist in core. 

Target LU Name: PurchaseOrderLineNopart,

Service: DocReferenceObject

Source LU Name:PurchaseRequisition 

Transformation Method: REQUISITION_NO

Error Text: Field [KEY_REF] is mandatory for category and requires a value

Best answer by Mathias Dahl

I could recreate the problem and I looks like it happens when Requisition No is empty in the purchase order line. It makes sense since it's that number that you try to connect the two LUs on. So, this is a limitation of the Object Connection Transformation rule that you have installed, that you need to know about.

View original
Did this topic help you find an answer to your question?

4 replies

Amila Samarasinghe
Superhero (Partner)
Forum|alt.badge.img+14

Hi @Inisha Subasinghe 

Does it work when you disable the OCT rule?

BR,

Amila S. - https://www.linkedin.com/in/amila-samarasinghe-b3285974/
I
1 person likes this
  • I
    Inisha Subasinghe
I
Do Gooder (Employee)
Forum|alt.badge.img+4

Hi @Amila Samarasinghe,

Yes, It worked when disabled.

Thanks

Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Mathias Dahl
  • Superhero (Employee)
  • 2883 replies
  • October 23, 2023

The OCT rule looks okay and this works in 23R2, in my environment. Try enabling the log window and see if you can find any details about the error from the database there.

/Mathias
Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Mathias Dahl
  • Superhero (Employee)
  • 2883 replies
  • Answer
  • October 23, 2023

I could recreate the problem and I looks like it happens when Requisition No is empty in the purchase order line. It makes sense since it's that number that you try to connect the two LUs on. So, this is a limitation of the Object Connection Transformation rule that you have installed, that you need to know about.

/Mathias

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings