1. A dynamic-web-services server-implemented method for publishing a dynamic web service, the method comprising: receiving, by the dynamic-web-services server from an Enterprise Application client, a recorded transaction map describing a recorded transaction between said Enterprise Application client and an Enterprise Application server, said recorded transaction map including metadata corresponding to a plurality of transaction fields, wherein said Enterprise Application client comprises an Enterprise resource planning (“ERP”) client, and wherein said Enterprise Application server comprises an ERP server; automatically generating, by the dynamic-web-services server, a service description framework for a new dynamic web service corresponding to said recorded transaction, including for each of said plurality of transaction fields: defining an input corresponding to the current transaction field; and storing said defined input in said service description framework; determining, by the dynamic-web-services server, a unique service identifier for invoking said new dynamic web service; persisting, by the dynamic-web-services server, said unique service identifier, said service description framework, and said recorded transaction map in a data store; providing, by the dynamic-web-services server, said unique service identifier to said Enterprise Application client; receiving, by the dynamic-web-services server, a first request from said Enterprise Application client to invoke said new dynamic web service according to a package of input data, said first request indicating said unique service identifier, said package of input data being received in a first format according to a first calling mechanism; retrieving, by the dynamic-web-services server, said recorded transaction map from said data store according to said unique service identifier; according to recorded transaction map, determining, by the dynamic-web-services server, at least one Enterprise Application API call for performing said recorded transaction, said at least one Enterprise Application API call requiring a second calling mechanism, different from said first calling mechanism; repackaging, by the dynamic-web-services server, said package of input data in said first format into repackaged input data in a second format that complies with said second calling mechanism; and using said at least one Enterprise Application API call, invoking, by the dynamic-web-services server, a remote Enterprise Application server to perform said recorded transaction according to said second calling mechanism, said at least one Enterprise Application API call, and said repackaged input data.