- SAP Community
- Products and Technology
- Enterprise Resource Planning
- ERP Q&A
- sales order condition does not appear consistently

Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content

sales order condition does not appear consistently

Former Member

- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content

on 07-11-2007 1:02 PM

130

Hi,

Please help me with the error that I'm currently experiencing because sales order condition does not appear consistently in the order although it was only inputted manually. I checked on the analysis of the particular condition type and below is the message that I found. Access not executed (Requirement 714 not fulfilled)

The requirement 714 was assigned for this access in the access sequence. This requirement was not met in the preliminary condition step and so the access was not executed. Can you please explain to me how to deal and resolve this issue?

Thank you and kind regards.

Reyna Agustin

- SAP Managed Tags:
- SD (Sales and Distribution)

Former Member

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content

07-11-2007
2:13 PM

Hi Reyna,

Check the routine 714 and what does it stand for. Then only the solution could be given.

chan

Former Member

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content

07-11-2007
2:05 PM

Hi Reyna,

The requirement 714 would be executed every time you refer to the access thru a condition type. The requirement would have few lines of code which would check various conditions. Only if all the validations are fulfilled the access would be used. If any one condition fails then that particular access would not be picked.

Would recommend you to have a break point in the requirement 714 and start punching the order. When the control reaches the program, execute it step by step and find out which condition is failing.

Regards

Nadarajah Pratheb

Former Member

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content

07-11-2007
1:40 PM

Hi Reyna Agustin,

Actually requirement has some coding in it, first that should be satisfied only then the Access will be executed.

You are saying that "sales order condition does not appear consistently "

It is due to the reason that

sometimes the requirment is getting fulfilled , so access is made, so condition record is found.

sometimes the requirment is not getting fulfilled , so access is not made, no condition record.

Can you please paste the coding of routine 714 so that It can be exactly told what is the requirement which has been coded in this routine.

Reward points.

Regards,

Gaurav Raghav.

Former Member

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content

07-13-2007
8:18 AM

Hi to all,

Here is the code for requirement 714. Please help me on this matter.

Thank you and kind regards.

FORM KOBED_714.

*CONSTANTS: lC_2 value '2'.

*DATA: l_remain type p Decimals 1.

*

sy-subrc = 4.

*

l_remain = komt2-kolnr mod lC_2.

*

IF l_remain eq 0.

check komk-kdgrp ne '50'.

ENDIF.

case komt2-kolnr.

when '01' or '02' or '03' or '04'.

check:

not komk-kunnr is initial,

not komp-upmat is initial.

when '05' or '06'.

check:

not komk-kunnr is initial.

when '07' or '08' or '09' or '10'.

check:

not komk-hienr01 is initial,

not komp-upmat is initial.

when '11' or '12'.

check:

not komk-hienr01 is initial.

when '13' or '14' or '15' or '16'.

check:

not komk-hienr02 is initial,

not komp-upmat is initial.

when '17' or '18'.

check:

not komk-hienr02 is initial.

when '19' or '20' or '21' or '22'.

check:

not komk-hienr03 is initial,

not komp-upmat is initial.

when '23' or '24'.

check:

not komk-hienr03 is initial.

when '25' or '26' or '27' or '28'.

check:

not komk-hienr04 is initial,

not komp-upmat is initial.

when '29' or '30'.

check:

not komk-hienr04 is initial.

when '31' or '32' or '33' or '34'.

check:

not komk-hienr05 is initial,

not komp-upmat is initial.

when '35' or '36'.

check:

not komk-hienr05 is initial.

when '37' or '38' or '39' or '40'.

check:

not komk-hienr06 is initial,

not komp-upmat is initial.

when '41' or '42'.

check:

not komk-hienr06 is initial.

when '43' or '44' or '45' or '46'.

check:

not komk-hienr07 is initial,

not komp-upmat is initial.

when '47' or '48'.

check:

not komk-hienr07 is initial.

when '49' or '50' or '51' or '52'.

check:

not komk-hienr08 is initial,

not komp-upmat is initial.

when '53' or '54'.

check:

not komk-hienr08 is initial.

when '55' or '56' or '57' or '58'.

check:

not komk-hienr09 is initial,

not komp-upmat is initial.

when '59' or '60'.

check:

not komk-hienr09 is initial.

when '61' or '62' or '63' or '64'.

check:

not komk-hienr10 is initial,

not komp-upmat is initial.

when '65' or '66'.

check:

not komk-hienr10 is initial.

when '67' or '68' or '69' or '70'.

check:

not komk-hienr11 is initial,

not komp-upmat is initial.

when '71' or '72'.

check:

not komk-hienr11 is initial.

when '73' or '74' or '75' or '76'.

check:

not komk-hienr12 is initial,

not komp-upmat is initial.

when '77' or '78'.

check:

not komk-hienr12 is initial.

when '79' or '80' or '81' or '82'.

check:

not komk-zpkunbg is initial,

not komp-upmat is initial.

when '83' or '84'.

check:

not komk-zpkunbg is initial.

when others.

sy-subrc = 4.

endcase.

sy-subrc = 0.

ENDFORM.

FORM KOBEV_714.

sy-subrc = 4.

case komt2-kolnr.

when '01' or '02' or'03' or '04'.

check:

not komk-kunnr is initial.

not komp-upmat is initial.

when '05' or '06'.

check:

not komk-kunnr is initial.

when '07' or '08' or '09' or '10'.

check:

not komk-hienr01 is initial.

not komp-upmat is initial.

when '11' or '12'.

check:

not komk-hienr01 is initial.

when '13' or '14' or '15' or '16'.

check:

not komk-hienr02 is initial.

not komp-upmat is initial.

when '17' or '18'.

check:

not komk-hienr02 is initial.

when '19' or '20' or '21' or '22'.

check:

not komk-hienr03 is initial.

not komp-upmat is initial.

when '23' or '24'.

check:

not komk-hienr03 is initial.

when '25' or '26' or '27' or '28'.

check:

not komk-hienr04 is initial.

not komp-upmat is initial.

when '29' or '30'.

check:

not komk-hienr04 is initial.

when '31' or '32' or '33' or '34'.

check:

not komk-hienr05 is initial.

not komp-upmat is initial.

when '35' or '36'.

check:

not komk-hienr05 is initial.

when '37' or '38' or '39' or '40'.

check:

not komk-hienr06 is initial.

not komp-upmat is initial.

when '41' or '42'.

check:

not komk-hienr06 is initial.

when '43' or '44' or '45' or '46'.

check:

not komk-hienr07 is initial.

not komp-upmat is initial.

when '47' or '48'.

check:

not komk-hienr07 is initial.

when '49' or '50' or '51' or '52'.

check:

not komk-hienr08 is initial.

not komp-upmat is initial.

when '53' or '54'.

check:

not komk-hienr08 is initial.

when '55' or '56' or '57' or '58'.

check:

not komk-hienr09 is initial.

not komp-upmat is initial.

when '59' or '60'.

check:

not komk-hienr09 is initial.

when '61' or '62' or '63' or '64'.

check:

not komk-hienr10 is initial.

not komp-upmat is initial.

when '65' or '66'.

check:

not komk-hienr10 is initial.

when '67' or '68' or '69' or '70'.

check:

not komk-hienr11 is initial.

not komp-upmat is initial.

when '71' or '72'.

check:

not komk-hienr11 is initial.

when '73' or '74' or '75' or '76'.

check:

not komk-hienr12 is initial.

not komp-upmat is initial.

when '77' or '78'.

check:

not komk-hienr12 is initial.

when '79' or '80' or '81' or '82'.

check:

not komk-zpkunbg is initial.

not komp-upmat is initial.

when '83' or '84'.

check:

not komk-zpkunbg is initial.

when others.

sy-subrc = 4.

endcase.

sy-subrc = 0.

ENDFORM.

Ask a Question

Related Content

- Pricing error in item 000010 in VF03. in Enterprise Resource Planning Q&A
- Condition workflow by Gross Price - Order and contract in Enterprise Resource Planning Q&A
- S/4 HANA Archiving conditions for account balances in Enterprise Resource Planning Q&A
- Using Responsibility Rules in Situation Handling (2/2) in Enterprise Resource Planning Blogs by SAP
- Using Responsibility Teams in Situation Handling (1/2) in Enterprise Resource Planning Blogs by SAP

Top Q&A Solution Author

User | Count |
---|---|

107 | |

6 | |

5 | |

4 | |

3 | |

3 | |

3 | |

2 | |

2 | |

2 |

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.