NOT VALID DELIVERING PLANT

Hi,
When i am entering the PLANT while trying to create a sales order, using the same customer for SP and SH,system is giving a message that delivering plant is not valid and the customer for the delivering plant is the same as the SOLD TO PARTY.But while creating customer master I ve assigned this plant as the delivering plant
plz help to solve
thanks,
smita

Hi,
Just to elaborate a bit on the neterprise stru assignment
Check the sales area that you are using to create a sales order.
Check if the sales area is assigned properly to the Credit Control area.
Check if the Delivering plant is assigned to the cos code.
Check if the sales org is assigned properly to the Cos code.
Check if the sales org and distribution channel is assigned to the plant.
Check if the Distribution channel is assigned to the sales org
Check if the Division is assigned to the sales org
Then create the material for the sales area and plant. or extend it for that plant by using MM50.
Lastly create a customer in the cos code and for the specific sales area.
If you do each step systematically then you wont face any probs.
Edited by: Christino Ronaldo on Aug 6, 2008 11:38 AM

Similar Messages

Error : Enter a valid delivering plant

Hi i have a below error, can u pls suggest.
Enter a valid delivering plant
Message no. V1 755
Diagnosis
The customer for the delivering plant is the same as the sold-to party.
System Response
The system cannot determine a valid delivering plant.
Procedure
Check if a delivering plant has been entered in the customer master, material master, or in the customer-info record, with identical customer and sold-to party.
Regards
Nawzir

You can maintain Plant in Sales Order at Header or / and Item level on Shipping tab page. You can go to shipping tab page for item level bt double-clicking on line item & then go to shipping tab page.
Alternatively maintain plant in master data as undere:
Customer-Material Info
Customer Master data
Material Master data
Regards,
Rajesh Banka
Reward points if helpful

Profit center to be based not on delivering plant but where revenue booked

< MODERATOR: Message locked. Please post this message in the [Controlling forum|SAP ERP Financials - Controlling;. >
Dear gurus,
we are implementing ECC 6.0 and have a branch wise profit centers.
say delhi is a profit center and Mumbai is a profit center
we have a profit center wise trial balance with doc splitting in place
Now sometimes a sale is to be recorded in Mumbai but the delivery of goods is to happen from Delhi.(eg different profit center)
The sales office are Mumbai and Delhi respectively.
As revenue is to go to Mumbai profit center but delivery from Delhi plant, the profit center taken is that of Delhi.
But this should not be the case
I want to substitute the profit center as Mumbai, even though the delivery is happening from Delhi Plant.
(each branch is a plant)
Can you suggest solution with detailed config to be done for this.
Regards,

Dear Piet,
Can you give details of the user exit.
Regards,

Intercompany Billing and Delivering Plant

Hi,
I had selected a delivering plant for my intercompany billing, that was different from the one previously assigned to my sales organisation and company code. However, even after cancelling those assignments, I still cannot use my original plant to process sales orders.
I keep getting the error message" enter a valid delivering plant"
Could you tell me how to resolve this issue and oblige?
Regards,
Aditya

Hi,
check whther the assignemnt for intecompany settings. The Delivering plant should be asigned to the ordering Sales org and distribution channel combination.
Prasanth

SAP Note 144253 For error Enter valid delivery plant in sales order

Hi all,
I am getting the error "Enter valid delivery plant" while creating the sales order . This is due to Customer and plant are same .
For that I got one SAP Note 144253.
If anyone implimented this SAP note Could you please share is there any impact of this note after implimenting.
Thanks
CM

Hi,
Go to bellow links,
http://help.sap.com/saphelp_nw04/helpdata/en/60/8def3981fe5d7de10000000a114084/content.htm
http://www.sap-basis-abap.com/bc/steps-to-install-sap-note.htm
Thanks,
Raviteja

Country of Delivering Plant is not showing in Sales Order Pricing Analysis

Hello All,
I have created a new condition table with the field Country of Delivering Plant (KOMK-WKCOU).
But in the sales order pricing analysis this field is not fetching the country of the plant (it is showing the Yellow color exclamation icon).
This is a standard field, I am not able to understand why it is not fetching this field.
I have used the same field for tax condtions in my previous projects as well, there it worked well.
Even I have activated the KOMK structure in SE11 also, but still the same problem.
Can anybody tell me how to resolve this issue.
Thanks & Regards,
Sreehari.

Rightly suggested by Shiva.
As plant determines at item level.
So, instead of KOMK-WKCOU, field should append in KOMP.
FYI, for checking any inconsistency in condition table, you can use TCode VK+C.
Regards
JP

Delivering Plant not visible

Hi Friends
I an unable ti understand why the delivering plant is not visible in the delivering plant field in a sales order. I have maintained the delivering plant in customer master but when i create the sales order the plant is visible at the item level but not at the header leve(on the front screen of sales order next to req. delivery date)
Can some one please help me with the solution.
Regards,
Wasim.

Hi Vishal,
Thanks for your feedback. My issue is when you are making a sales order using VA01 on the first screen itself there is the field of delivering plant in the middle of the screen next to the required delivery date. This field is different than the plant field at item level.
I want to populate this field with the delivering plant. But when I enter the plant in this field it is not getting saved. What could be the problem and the possible solution.
Plz help, its very critical.
Regards,
Wasim.

Delivering plant problem

hi,
I am maintaining delivering plant at customer master level,
material master level and even in customer info record...
but at the time of sales order its not picking the delivery plant...
even if i enter it manually also its saying.. not a valid delivery plant.
regards,
ram

A Plant becomes a Delivering Plant onlt if it is assignned to combination of Sales Organization and Distribution Channel. As suggested in earlier response maintain the configuration appropriately.
Enterprise Structure Configuration (SD view point):
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Regards,
Rajesh Banka

Delivering plant's maintenance and determination on sales order

Hi
We would need to maintain delivering plant on vendor level for sales order but as this is not possible we might want to maintain it on article master data. Our biggest problem si the time perspective. It should be possible to maintain the plant so that it has a validity period. An article's delivering plant might hence change in the future and the sales order items that have a delivery time after this date should get the new plant. We have a huge amount of articles and a huge amount of sales orders so manual maintenance of each sales order item is out of question.
Any suggestions for soving this? Amount of articles and sales order item is so big that manual maintenance is not possible. Sales order items are also created far to the future.
Thanks and br
Seija

Welcome to SDN forum.
Well, the delivering plant is proposed from the the ship-to party customer master.
Provided the ship-to party is different from the sold-to party.
So, if you have same partner numbers to ship-to party & sold-to party then preference will go to sold-to party.
Say,
Case1
Sales Partner
Customer Number
Delivering Plant
maintain in respective customer master
SP - Sold-to Party
ABC123
ZY02
SH - Ship-to Party
ABC123
ZY01
In above case, the delivering plant ZY02 will be from sold to party.
Case2
Sales Partner
Customer Number
Delivering Plant
maintain in respective customer master
SP - Sold-to Party
ABC123
ZY02
SH - Ship-to Party
ABC321
ZY01
In above case, the delivering plant ZY01 will be from ship-to party.
Regards
JP
Here I have assumed that delivering plant determination is happening on based on customer master

Error-BOM is not valid

Hi all,
i am creating a BOM with item & sub item .
i am getting the error like BOM is not valid.
i am giving my coding below.plz suggest where i am doing mistake.
it's urgent.
can u plz give some sample coding where sub-item will be there in that BOM.
any idea will be highly appreaciated.
correct answers will be rewarded.
regards
pabitra
report z_bom_create
       line-size 132
       line-count 65.
      no standard page heading.
*-- DATA DECLARATION--
include <icon> .
*---Tables
tables : s076, t100, marc .
*---Types
types : begin of t_upload,      " Upload file data
         col1(18),
         col2(10),
         col3(30),
         col4(12),
         col5(50),
       end of t_upload,
       begin of t_split,
       location like stpu-ebort,
       end of t_split.
*data:begin of i_return occurs 10.
*include structure bapiret2.
*data:end of i_return.
data:i_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
types:begin of t_item."occurs 10.
include structure BAPI1080_ITM_C.
types:end of t_item.
types:begin of t_subitem." occurs 10.
include structure BAPI1080_SUI_C.
types:end of t_subitem.
types:begin of t_header." occurs 10.
include structure BAPI1080_MBM_C.
types:end of t_header.
types:begin of t_bomgroup." occurs 10.
include structure BAPI1080_BGR_C.
types:end of t_bomgroup.
types:begin of t_variant." occurs 10.
include structure BAPI1080_BOM_C.
types:end of t_variant.
data:it_itemas LIKE bapi1080_rel_itm_bom_c OCCURS 0 WITH HEADER LINE,
     it_subitemas LIKE BAPI1080_REL_SUI_ITM_C OCCURS 0 WITH HEADER LINE.
*--- Tables
data: i_upload type standard table of t_upload, " to hold data
      i_upload1 type standard table of t_upload,
      i_upload2 type standard table of t_upload,
      i_split type standard table of t_split,
      i_item type standard table of t_item,
      i_subitem type standard table of t_subitem,
      i_header type standard table of t_header,
      i_bomgroup type standard table of t_bomgroup,
      i_variant type standard table of t_variant.
data: wa_upload type t_upload, " to hold file data,
      wa_upload1 type t_upload, " to hold plan data,
      wa_upload2 type t_upload,
      wa_split type t_split,
      wa_item type t_item,
      wa_subitem type t_subitem,
      wa_header type t_header,
      wa_bomgroup type t_bomgroup,
      wa_variant type t_variant.
data:v_matnr like mara-matnr,
     v_start like sy-index,
     v_count(3) type c,
     v_num(4) type c value '0000'.
*--Constants
data: c_dot type c value '.',
      c_x type c value 'X',
      c_comma type c value ','.
-------Selection Screen Design -
*Selection screen for input of upload file address
selection-screen skip 2.
selection-screen begin of block blk1 with frame.
parameters     : p_file like rlgrap-filename obligatory .
parameters     : p_matnr like mara-matnr obligatory,
                 p_werks like marc-werks obligatory memory id wrk,
                 p_stlan like afko-stlan obligatory default '1' .
selection-screen end of block blk1.
---AT SELECTION SCREEN -
*at selection-screen on value-request for p_file.
**--For popup to select file.
perform f_give_help.
*at selection-screen on p_matnr.
perform f_check_matnr.
-----START OF SELECTION -
*--Data upload using WS_Upload.
perform f_get_data.
perform f_get_bom_data.
perform f_get_bom_data1.
perform f_call_bapi.
perform f_error_display.
*&      Form f_give_help
      text
--> p1        text
<-- p2        text
*FORM f_give_help.
*call function 'WS_FILENAME_GET'
      exporting
           mask             = ',.,..'
           mode             = 'O'
      importing
           filename         = p_file
      exceptions
           inv_winsys       = 1
           no_batch         = 2
           selection_cancel = 3
           selection_error = 4
           others           = 5.
if sy-subrc <> 0 and not sy-msgty is initial.
   message id sy-msgid type sy-msgty number sy-msgno
   with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*ENDFORM.                    " f_give_help
*&      Form f_check_matnr
      text
--> p1        text
<-- p2        text
*FORM f_check_matnr.
*CALL FUNCTION 'BAPI_MAT_BOM_EXISTENCE_CHECK'
EXPORTING
   MATERIAL              = p_matnr
   PLANT                 = p_werks
   BOMUSAGE              = '1'
VALID_FROM_DATE       =
VALID_TO_DATE         =
TABLES
   RETURN                = i_return.
*ENDFORM.                    " f_check_matnr
*&      Form f_get_data
      text
--> p1        text
<-- p2        text
FORM f_get_data.
call function 'WS_UPLOAD'
   exporting
CODEPAGE                      = ' '
      filename                      = p_file
      filetype                      = 'DAT'
    tables
      data_tab                      = i_upload
   exceptions
     conversion_error              = 1
     file_open_error               = 2
     file_read_error               = 3
     invalid_type                  = 4
     no_batch                      = 5
     unknown_error                 = 6
     invalid_table_width           = 7
     gui_refuse_filetransfer       = 8
     customer_error                = 9
     others                        = 10
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
ENDFORM.                    " f_get_data
*&      Form f_get_bom_data
      text
--> p1        text
<-- p2        text
FORM f_get_bom_data.
delete i_upload where col1 is initial.
delete i_upload where col1 cs 'ITEM'.
i_upload2[] = i_upload[].
delete i_upload2 where col1 cs 'FINISHED GOOD'.
read table i_upload into wa_upload with key col1 = 'FINISHED GOOD:'.
if sy-subrc = 0.
v_matnr = wa_upload-col2.
if v_matnr <> p_matnr.
message e001(zl) with p_matnr.
endif.
else.
message e000(zl).
endif.
ENDFORM.                    " f_get_bom_data
*&      Form f_get_bom_data1
      text
--> p1        text
<-- p2        text
FORM f_get_bom_data1.
loop at i_upload into wa_upload where col1 CS 'FINISHED GOOD'.
v_start = sy-tabix + 1.
loop at i_upload into wa_upload1 from v_start .
        if wa_upload1-col1 cs 'FINISHED GOOD'.
          exit.
        else.
perform f_split_upload_data.
     endif.
endloop.
      endloop.
ENDFORM.                    " f_get_bom_data1
*&      Form f_split_upload_data
      text
--> p1        text
<-- p2        text
FORM f_split_upload_data.
if not wa_upload1-col5 is initial.
if wa_upload1-col5 cs c_comma.
split wa_upload1-col5 at c_comma into table i_split.
loop at i_split into wa_split.
v_count = v_count + 1.
endloop.
if wa_upload1-col4 <> v_count.
   wa_upload1-col4 = v_count.
endif.
clear wa_upload1-col5.
clear wa_split.
clear v_count.
loop at i_split into wa_split.
wa_upload1-col5 = wa_split-location.
append wa_upload1 to i_upload1.
endloop.
else.
append wa_upload1 to i_upload1.
endif.
else.
append wa_upload1 to i_upload1.
endif.
clear wa_upload1.
ENDFORM.                    " f_split_upload_data
*&      Form f_call_bapi
      text
--> p1        text
<-- p2        text
FORM f_call_bapi.
clear wa_upload1.
wa_header-material = p_matnr.
*wa_header-plant = p_werks.
wa_header-bom_group_identification = 'BAPI_SMP_COL1'.
wa_header-bom_usage = p_stlan.
wa_header-alternative_bom = '1'.
append wa_header to i_header.
wa_bomgroup-bom_usage = p_stlan.
*wa_bomgroup-created_in_plant = p_werks.
*wa_bomgroup-bom_group = ''.
wa_bomgroup-object_id = 'SIMPLE1'.
wa_bomgroup-bom_group_identification = 'BAPI_SMP_COL1'.
wa_bomgroup-object_type = 'BGR'.
append wa_bomgroup to i_bomgroup.
wa_variant-alternative_bom = '1'.
wa_variant-base_qty = '1.000'.
wa_variant-valid_from_date = sy-datum.
wa_variant-bom_group_identification = 'BAPI_SMP_COL1'.
wa_variant-object_type = 'BOM'.
wa_variant-object_id = 'VAR'.
wa_variant-bom_status = '1'.
wa_variant-valid_from_date = sy-datum.
wa_variant-function = 'NEW'.
append wa_variant to i_variant.
it_itemas-bom_group_identification = 'BAPI_SMP_COL1'.
it_itemas-sub_object_type = 'ITM'.
it_itemas-sub_object_id = 'SIM'.
it_itemas-super_object_type = 'BOM'.
it_itemas-super_object_id = 'VAR'.
it_itemas-valid_from_date = sy-datum.
it_itemas-function = 'NEW'.
append it_itemas.
it_subitemas-bom_group_identification = 'BAPI_SMP_COL1'.
it_subitemas-sub_object_type = 'SUI'.
it_subitemas-sub_object_id = 'SIMP'.
it_subitemas-super_object_type = 'ITM'.
it_subitemas-super_object_id = 'SIM'.
append it_subitemas.
loop at i_upload2 into wa_upload2.
*wa_item-item_id = v_num.
*v_num = v_num + 1.
wa_item-bom_group_identification = 'BAPI_SMP_COL1'.
wa_item-object_type = 'ITM'.
wa_item-object_id = 'SIM'.
wa_item-item_no = wa_upload2-col1.
wa_item-item_cat = wa_upload2-col2.
wa_item-component = wa_upload2-col3.
wa_item-comp_qty = wa_upload2-col4.
wa_item-valid_from_date = sy-datum.
append wa_item to i_item.
endloop.
loop at i_item into wa_item.
loop at i_upload1 into wa_upload1 where col1 = wa_item-item_no.
wa_subitem-bom_group_identification = 'BAPI_SMP_COL1'.
wa_subitem-object_type = 'SUI'.
wa_subitem-object_id = 'SIMP'.
IF not wa_upload1-col5 is initial.
on change of wa_upload1-col5.
v_num = v_num + 1.
wa_subitem-subitem_no = v_num.
wa_subitem-subitem_qty = '1'.
wa_subitem-installation_point = wa_upload1-col5.
append wa_subitem to i_subitem.
clear wa_subitem.
endon.
endif.
clear wa_upload1.
endloop.
clear v_num.
clear wa_upload.
endloop.
CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'
EXPORTING
TESTRUN                  = ' '
ALL_ERROR                = ' '
TABLES
    BOMGROUP                 = i_bomgroup
    VARIANTS                 = i_variant
   ITEMS                     = i_item
   SUBITEMS                  = i_subitem
    MATERIALRELATIONS        = i_header
   ITEMASSIGNMENTS           = it_itemas
   SUBITEMASSIGNMENTS        = it_subitemas
TEXTS                    =
    RETURN                   = i_return.
*if i_return[] is initial.
*CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
*write: /'BOM created:', stpo-stlnr.
*else.
*if not i_return[] is initial.
*loop at i_return.
WRITE:/ i_return-type, i_return-id, i_return-number,
         i_return-message.
*ENDLOOP.
   IF i_return-TYPE = 'E'.
   errmsg-type = i_return-type.
   errmsg-line = i_return-message.
   append errmsg.
     ULINE /1(108).
     write:/ icon_led_RED as icon, i_return-MESSAGE.
     ULINE /1(108).
   ENDIF.
   IF i_return-TYPE = 'W'.
   errmsg-type = i_return-type.
   errmsg-line = i_return-message.
   append errmsg.
     ULINE /1(108).
     write:/ icon_led_YELLOW as icon, i_return-MESSAGE.
     ULINE /1(108).
   ENDIF.
ENDLOOP.
**write: / i_return-id, i_return-number, i_return-message(80).
**endloop.
**write: /'Error'.
**endif.
ENDFORM.                    " f_call_bapi
*&      Form f_error_display
      text
--> p1        text
<-- p2        text
FORM f_error_display.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
loop at i_return.
WRITE:/ i_return-type, i_return-id, i_return-number,
          i_return-message.
ENDLOOP.
ENDFORM.                    " f_error_display

Are u sure That BAPI is the right one to use to create BOM , I think this Error is coming from BAPI itself So try to Debug the BAPI from where its throwing the error.
Regards
prabhu

How to update the Delivering plant in sales order

Hi Guru's
I have a scenario where the delivering plant(RV45A-DWERK) in the sales order overview is not updated.
I have maintained the VD51 customer info record
in customer master and also in material master.
Even if i update manually in the sales order and then save it is not updating
when i got va02 and check it is blank
regards
sphoorthi

***Hi,***
***As replied by many ,Plant is determined from CMIR/MATEIRIAL MASTER/CUSTOMER MASTER.***
***First check by maintaining plant in CMIR and check whether it is determined in SALES ORDER?***
***Before that check in VOV8 in document type check the field "Read inford record",***
***then check by maintaining plant in Customer master,and check if determined in SALES ORDER?***
***then check by maintaining plant in material master and check if deterimined in SALES ORDER?***
***If still ,problem then u can check the user exits,***
***Thanks***
***Jai***

Delivering plant on sales orders

Hello
I know that if I access to transaction XD02 under Sales Area Data on Shipping tab, I can set the Delivery Plant field, in order to take it automatically when I create a new sales order for that client, but, I am able to change it, does anyone know a way to lock it in order to no one could change it at sales order?
Thank you in advance
Regards

I saw that I was able to change it on the sales order,
Sorry by oversight, I have not seen this comments. To achieve this requirement in sale order, I am not sure whether your requirement is at header level or item level. If I am correct, for header level delivering plant, the object name is C_AFKO_AWK which you have to change this field to display with the help of your basis team.
thanks
G. Lakshmipathi

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
#       mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
#   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
#   For example, you define $mydestination domain recipients in
#   the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

The material does not exist in plant or flagged for deletion

Hi All,
I have done the integration of R3 back end with SRM system (SRM 5.0) Classic scenario is working fine.
In the direct Material Procurement I get an error message that "the material does not exist in plant or flagged for deletion".
I checked R/3 side material is active only and I have assigned plant in extend attributes.
Can you please help me to resolve this problem..
Thanks
Ravi

Hi Ravi
check you validit date from and to for that material in comm_product table.* if it is valid you can do shopping or else you cant.
regards
Muthu

How to download Delivering Plant of R/3 Customer Master in CRM BP

Hi,
We have successfully downloaded the Plants from ECC to CRM using the object DNL_PLANT which has successfully created BP's for PLants in CRM with BP Role=Plant and have updated the mapping in table CRMM_LOCMAP.
Now I want that the Delivering Plant mantained in ECC Customer Master Data (XD02 -> Sales Area Data -> Shipping Tab -> Delivering Plant Field) to be updated in the CRM Business Partners as BP Relationship.
The BP(Customer BP) should be updated as a BP Relationship "ZPLANT - Has Plant" with BP(BP of the Plant in CRM). This is not happening.
Can you please tell me the Steps to be performed in both CRM and ECC side to bring the ECC Delivering PLant as Relationship in CRM ?
Is the Delivering Plant change in ECC Customer Master Data does not gets captured in the BUPA_MAIN BDoc ?
When we change the Delivering Plant in ECC Customer Master Data, a BUPA_MAIN Bdoc gets triggered but when we look into the Bdoc we can not find the changed information of the Delivering Plant. I am not usre if this behaviour is right or not.
There is an OSS Note - 493947 which is quite old and talks about creating a Customer each for all the Plants in ECC and creating a Partner Function for Plant in the Customer Master Data. I am not sure if this process is still to be followed Or SAP has given some stadard settings to bring ECC Delivering Plant mantained in Customer Master to CRM.

To my knowledge oss note 493947 is still relevant
Edited by: Anders Brock-Faber on Apr 6, 2009 1:06 PM

NOT VALID DELIVERING PLANT

Similar Messages

Maybe you are looking for